I have some scenarios that am not really sure about regarding TestFlight and AppStore:
The user has version 1.0 installed on device from TestFlight and then he updates to the same version 1.0 from AppStore. What happens, the build is just overwritten?
The user has version 1.0 installed on device from TestFlight and then he updates to a newer version 1.1 from AppStore. What happens, the build is just overwritten? What is the difference between this case and the previous one?
The same as case 1. does the user receive any notification that the application is available on AppStore?
Any other observations are appreciated.
Thank you very much! :)
To answer 1 & 2 :-
Yeah the app will be overwritten. It will be like a regular app update from the app store. All the data that is saved in the test flight app also will be preserved when you install the app from app store.
Question 3 - No there will not be any notification in the testflight app if the application is available in the app store.
Related
Say for example internal and external testers under TestFlight are testing the application. Then a live Appstore release that was uploaded previously gets approved. Will the current testers get the new app update which will override the current test build?
Any feedback is greatly appreciated.
Testing
Once you accept your invitation, you’ll be able to download a beta version of the app you’ve been invited to test. If you already have the live app installed on your device, the beta version of the app will replace the live version. When you’ve downloaded the beta app, you’ll see an orange dot next to its name that identifies it as a beta. TestFlight will notify you each time a new build is available and provide instructions on where to focus. You can easily offer feedback by tapping the Provide Feedback button in the App Details view in TestFlight. An email automatically opens with pertinent app and device details, and you can add additional details and screenshots.
The beta period lasts for 60 days, starting on the day it is released
to testers. In TestFlight, the number of days remaining appears below
the Open button for each app.
If a beta app has In-App Purchases, you do not have to purchase them,
as In-App Purchases made with beta builds are free within the context
of the beta version.
Quote from this link
Tester won't get notified whether the original app is approved by Apple or not. If the app is approved, then user have to download app via App Store. But if tester downloads app from App Store, then it's gonna override the test version.
Apple developer site says
When the app becomes Ready for Sale in the App Store, testing automatically stops on earlier builds, and you will be unable to view or test them.
Refer this link
I think the tester will get an email saying the app has been updated and approved. Since the normal upload will be notified by an email, but haven't tried it ,
TestFlight testers will get notification by email and after app live beta version of app will be unavailable and when they update their app they get live update app.
I currently have App v1.0 approved for beta testing to external testers and have sent out the appropriate email.
I recently also submitted App v1.0 for AppStore and is waiting for review.
My question is, once the app has been approved for download on the AppStore, will users be notified to update the existing beta test App to the one available on the AppStore "when" they open the AppStore app, or will it be a separate App where they have to search for it and download it?
I found a similar question here: Update application to AppStore listed app from TestFlight beta app
However, the answer provided did not directly answer the question I have.
I also found this:
Will testflight prerelease beta app version update existing App Store version, or install another instance of the app on tester's device?
However, that's the opposite of what I'm asking.
Thanks.
I don't think so. In my experience, the test flight version is not seen as an app store app, so no update will be suggested. In addition, test flight users will typically have an equal or greater version number than the app on the app store, so there would be little point to "updating" to the app store version.
We are going to submit a prerelease version of an app to external users, but I wonder: what will their experience be?
The user had a production App Store version of the app on the device, and now installs a new beta via TestFlight. Will this be in-place update, with the data preserved, or a completely new install with data wiped, or will TestFlight's version be installed next to production - so that the user has the app twice?
Testing is over, and the production-ready version is submitted to the App Store. Will the tester be able to update to the new App Store version seamlessly (in-place), with the beta version's data preserved? Or is it a complete wipe? Or will beta stay on his device and he has to download a new full version from scratch?
By the way, I have submitted another question regarding version numbering beta vs. production.
According to https://developer.apple.com/testflight/
Once you accept your invitation, you’ll be able to download a
beta version of the app you’ve been invited to test. If you already
have the live app installed on your device, the beta version of the
app will replace the live version. When you’ve downloaded the beta
app, you’ll see an orange dot next to its name that identifies it as a
beta. TestFlight will notify you each time a new build is available
and provide instructions on where to focus. You can easily offer
feedback by tapping the Provide Feedback button in the App Details
view in TestFlight. An email automatically opens with pertinent app
and device details, and you can add additional details and
screenshots.
It's said that the beta version of the app will replace the live version. The reason is the beta app has exactly the same bundle identifier with the one on the App Store.
After installing the beta app, the user will still see the updates from the App Store as the live version has been installed (without losing any data) because the beta app is deployed using exactly the same certificate.
I think the things changed a while ago.
Even if you have a beta (which is signed with production certificate - remember, no AdHoc needed), the TestFlight version will function as an update for the existing app. I tested those things and can confirm no NSUser defined entities were overwritten or deleted by the TestFlight build.
For the second part: the user can preserve saved data if the application is not a major build (I mean, you cannot expect a database stored in some format to work with another new model of your app version). To be sure your app does not clear or attempt to modify previous content, put a version check on the new one. If there are data found, update to the new schema. I think this is the way to go. Anyway, you cannot have duplicated versions of the app because they are signed by the same profile.
I got rejected from Apple Review Team 2 times (It take about 20 days).
Reason
2.2 - Apps that exhibit bugs will be rejected Thank you for resubmitting your app for review.
2.2 Details
In continuing our review, we discovered that your watch app did not
install on the Apple Watch after the app was installed on iPhone 6
running iOS 8 on both Wi-Fi and cellular networks.
Next Steps
It would be appropriate to revise your app to ensure that the user is
able to access this feature.
My Question is how we submit App with apple watch app without rejected with install problem.
From rejected information that I got.
1 st submission Rejected because I set Build Active Architecture only to YES.
2 nd submission Rejected (Again) with feedback "app did not install on the Apple Watch after the app was installed on iPhone 6 running iOS 8 on both Wi-Fi and cellular networks."
I have been test with TestFlight it also installed successful with my iPhone6+ and Apple Watch.
I don't know next step what should I do to fixed this issue.
Anyone have any ideas?
You should be able to dispute it. I would tell them that it installs just fine with test flight and on a physical device. Click on your rejected app and click on Resolution Center.
You can also send them screenshots. Take some of the physical device. Hell... send them real photographs.
I disputed a rejection on an app update and it was accepted a few days later.
I doubt this is an issue but make sure you're signing with proper certificates and profiles as well... but let them know that they're most likely at fault (and that their whole system is stupid.)
They probably couldn't install the app on their devices because they have all of their "smart" people on their "change spotify" project.
Follow-up question to: this question
I submitted version 3.4 of my app for app store review. Then I enabled beta testing for that same build. Apple has (imo incorrectly) rejected that beta review build, while my app store submission still says "Waiting for Review".
My question is: does the beta rejection in any way affect the app store submission? In other words, can I ignore the beta rejection and plunge ahead with the app store build? (I don't want to wait 2 weeks only to find out that their web-site does not correctly handle this case.)
Apple's review process applies to all beta builds sent through their TestFlight service on iTunes Connect. Your build has failed this review process.
The AppStore process is identical. Your build will also fail there (if they even let you submit for review).
Only a single data-point, but I have had exactly the same binary fail the Testflight Beta review and pass the full app store review. Both were in review in parallel (I had a good release candidate but wanted to use the Beta process to get a version out quicker for some additional translation testing).
In this specific example, the app was slow(ish) to start (it downloads a lot of data for offline use) and I think the Testflight Beta reviewer was just less patient!