I am a new at this and I have been trying to update my new release APK but when the Play store reviews it they rejected with an screenchot of the first APK instead of the new one. What am I doing wrong?
In my experience, if your app was ever rejected, sometime it may appear in Play Console [Publishing overview] with "Changes you make won't be sent for review automatically" and [Send for review] button.
Press [Send for review] button to let it be reviewed. Hope this is helpful.
Related
I published an Android TV app in the play store. I opted in for the Android TV by visiting Setup > Advanced Settings > Release Types. It was later rejected for valid reasons and I received an email.
Now, I fixed the issues and published a new version.
I was expecting the Rejected status to change to In Review in the Android TV section in Advanced Settings.
But, sadly, it just shows Update rejected. It is not clear, if it means the new update is rejected. I did not get any email. Even the error message in the "Policy" section only shows the last rejection details and date also reflects the first rejection.
Now, I think, the review is not even initiated after publishing the update. How can I initiate the review? I tried opt-out ⇨ save ⇨ opt-in. Even then, it does not go to in review status.
Any help is appreciated...
Note that the newer version of the app is approved as a regular app. The reject is only on the Android TV.
You'll need to check it on the Production page and then the Releases tab
I uploaded a new version of my app into TestFlight it’s the Version 0.2. My previous version was 0.121.
After the new version 0.2 was accepted, no one got a push notification to update the app.
Everyone has to click on the public link again or open TestFlight.
Is it possible to send a new notification to all users?
My solution: Edit the test information and you'll get immediately a push notification.
Since Apple moved to their new and improved TestFlight website, none of my internal or external users are receiving push notifications or emails when I make a new build available for testing.
These are testers who previously were getting push and emails with each new build.
If the tester goes to the TestFlight app on their device, they do see the new build is available for update there.
I see a couple threads about this in the Apple Developer forums but nobody seems to know how to work around this problem:
https://forums.developer.apple.com/thread/76020
https://forums.developer.apple.com/thread/76131
Anyone here found a workaround for this problem?
when submitting a build for beta approval, uncheck 'automatically notify' in lower left corner. then after beta is approved for external testing, click 'notify testers' in upper right corner. if i recall next time i do this, i'll include screenshots.
this solution is from #boozedog, it fixed the issue for me, and i am submitting #boozedog's comments as an answer. the text of his comment:
"
The Automatically Notify checkbox appears in the bottom left of the dialog box when you submit the build to beta approval on the iTunes Connect website. Make sure you clear that checkbox. And then, after the beta approval is complete, go back in to that build in iTunes Connect website and you should see an action button in the top right corner "Notify Testers."
"
Well, I submitted an app to the app store, but my little cousin went on my computer and screwed up the project so badly that I had to start from scratch. So I rebuilt everything back to how it was, and I am trying to submit it to the app store and it obviously isn't recognizing it as the same app,
(Please make sure that you have set up a record for this application
on iTunes Connect.)
although the bundle ID is the same as the old one. How can I go about doing this? I have to get this update out fast, any replies are greatly appreciated!
Have you prepared the app in iTunesconnect to receive an update?
After you have chosen to "Add version", you still have to press the button "Ready to upload binary" in the top right corner of the details screen of the app.
It should be sufficient to keep the app bundle the same in order to update.
You also have to use the same provisioning profiles as you used before.
I just want to see if I am going crazy or not. I have the following App Ids in the provisioning portal.
com.foo.*
com.foo
com.foo.FooApp
The first was for before we needed push.
The second was a mistake, but I can't delete it.
The third is for my current push notifications
The problem that I have is that the APNS assistant will not launch when I click the configure button for my com.foo.FooApp App Id. I created the push certificates and then revoked them, but am unable to recreate...?
Thanks!
mark
I have the same problem. The APNS assistant doesn't launch when I click the configure button. Tried everything I can think of, like creating additional AppID's and then trying to configure the SSL certs for those, but same result - clicking the configure button does nothing.
Also reported it to Apple (2010/10/12) -no response yet.
Just tried again (2010/10/15) - Apple fixed the issue. All working