I tried to publish alpha version of my app but I accidentaly promoted it to PROD. I entered Store Presence->Pricing & distribution and unpublished it as soon as possible.
How can I now start alpha/internal tests without going to prod with my previous release?
I've started new Alpha Release and it's in "Full rollout" but no Opt-in URL is available. It still says "An opt-in link will be available here when you publish your app."
Can I start new alpha without going to prod with previous 'buggy' version?
If you've previously not released your app on any track you'll need to start rollout for the alpha track. Then your app will be reviewed and you will get an opt-in URL.
The opt-in link only shows when an app is "Published." Apps in "Draft" or "Pending publication" won't show the opt-in link.
https://support.google.com/googleplay/android-developer/answer/3131213
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 have uploaded an app the play console and it is now on the Play Store but says (Beta). I was just wondering how do I publish the full version?
You promote the Production Track. Please note that if you are enrolled on a testing track you will still see Beta next to your app name, however if you use another Google Account that is not enrolled, you should not see Beta.
We have a published app in the Teams App Store.
And we are updating valid domains list from time to time (Adding new valid domains).
So we have to be sure that all users have latest version of the app.
If someone has old version of the app (without this valid domain name) they will not be able to open that site in task module window.
It is very important to keep the app updated.
So as we expected users are experiencing issues with valid domain names.
And the simple question "which app version does user have" led us to next issues: lack of a basic functionality on Mobile versions of the Teams app and a bug on the Desktop/Browser versions of the Teams app.
Mobile apps: There's just no way of getting app version. Or at least we haven't found it.
Desktop/Browser apps: There's 'About' tab with the description of the app and it's version. But in our case the text is long and the section is not scrollable so users can't scroll up and get app version. Check the screenshot below
Is there a way of updating the app for all our users of all tenants ?
Any help would be appreciated.
#Oleksa, #Hilton - Process of updating the version of the app is similar to how you submit the app initially to store.
Teams does not force users to update to latest available version of the App but it shows small banner with the message "latest version of the app is available" which user has to go and update to the newer version.
I am surprised, #Hilton did not have this question till now :)
As of (19/1/2021), You can only upgrade an app on desktop and not on mobile. Upgrading the app on desktop will automatically do the same on mobile.
I have released one version on my Application on iTune and is in process to release second one. Now I have uploaded the the .ipa file of the application and switching on for internal testing. But the application is not appearing on Testflight app of internal tester. I am uploading the .ipa file through Xcode 6.1 and also trying with Xcode 6.3.
When you upload the app on iTunes, then you can not add new IPA in existing version of app.
Make sure that for your app you have turned the switch ON for TestFlight Beta Testing.
Once done with that go to Internal Testers tab and check the internal testers from the list and invite them. Thats it! Hope it helps :]
Cheers!
If you've uploaded a build for the next/new version, you should see it at the top of the list of builds under the "Prerelease" menu for your app.
Assuming you're Build is in the list, check the "Internal" column for that build. If it says "Invite Testers", then that build is not yet active. What you probably need to do then is click the build number and make sure all the fields are filled out - especially "What to Test" - and then click the Save button. When you go back to the Builds list, it should now say "Active (30 Days Left)" under Internal. And should show up for testers in the TestFlight app.
I've noticed that sometimes I need to go through this process for a new build (even on a version I've already been testing) and sometimes I don't. I haven't found the pattern but it's tripped me up several times.
My app is ready to upload. Everything works fine in development side. I wonder what I should change (about SSL or something else) before uploading to store?
This is a complex topic and we may not be able to answer this in once sentence.
For submission you may need a Distribution Profile from the Apple Dev Center. Depending on the functionality you're using in your app, and depending on if it's an iOS or Mac App, you may be able to use the provisioning profile Xcode has generated for you. You can set this under Build Settings - Code Signing - Provisioning Profile.
You also need to setup your app in iTunes Connect so you can submit it (this includes screenshots, App Store Category, description, etc).
To check if the submission will be successful, head over to Product - Archive, and from the screen that opens hit "Validate". This will tell you if you're missing anything.
Take a look at the App Distribution Guide for details on how to submit an app to the App Store. There's a whole chapter on Push Notifications in there too which deserve special attention: https://developer.apple.com/library/ios/documentation/IDEs/Conceptual/AppDistributionGuide/SubmittingYourApp/SubmittingYourApp.html
Those technicalities aside, make sure that any NSLog and NSAssert statements that you may have used while developing are removed or not compiled before submission.