![]() The first step is to make your app hard to access. The caveat here is you’ll still have to publish to production, but using these two strategies, your app will be hard to access and impossible to install. However, I discovered a more suitable alternative for my project, and it may be more suitable for yours as well. ![]() This was the option Google Support suggested to get me unstuck. Your old bundle identifier cannot be reused and will forever be assigned to your production release, even if it’s not yet published. Abandon your current Android app record in the Google Play Console and create a new one with a brand new bundle identifier. There are a couple of options that may help get you unstuck. Perhaps this constraint is preventing you from publishing any new releases to your internal, closed, and open testing tracks because your app isn’t quite ready to be available on the store yet. There currently isn’t a way to cancel a pending production release in the Google Play Console.
0 Comments
Leave a Reply. |