I have archived and uploaded the build file of my swift application to iTunes Connect and started to use TestFlight Beta Testing with internal testers from my developing team. After a while, I have made some updates and bug-fixes (as expected :)), archived new version, uploaded the new build file to iTunes Connect and disabled the old application. However, when the testers had installed the new app, they have started to face crashes while application is launching and there is not any crash report generated. I am using the same version without any crash/problem installing the app directly from XCode via cable, but people who are installing via iTunes Connect keeps crashing. I am checking my iTunes Connect again and again. I have updated version info in Versions segment, enabled TestFlight Beta Testing for new version (it automatically disabled the older one).
Testers have tried deleting the old version from their devices, but still crashing. What might be the problem?
Related
I have created a Flutter Application. I have used Xcode Version 13.1.
I have created all the certificates that are necessary for the development and distribution. Previously I have uploaded around 5 builds for which I have invited the internal and external users as Testers. Those builds are working fine for the testing.
From build no 6 I started facing this strange issue "The requested app is not available or doesn't exist."
I tested the build before it is being uploaded in the TestFlight. It's working fine and also the app moves to Ready to Submit status as well.
From the 6th build i just upgraded my Flutter SDK version to 3.0 and later downgraded this and tried the build.
I tried with a different build by varying the plist data, but nothing works for us. I checked on my mac for the various certificates for this application and they are all good and valid.
I don't understand why for this application I have this behaviour.
Step that i have done:
I built the app.
I tested it on my iPhone.
From Xcode, I made an archive and uploaded it to TestFlight.
The archive has been received by Apple. It was then processed by Apple.
And finally, I received a notification that it was available on TestFlight.
While downloading the app it shows this error message.
But the build is there in the TestFlight.
Someone would have any idea?
Assume the there is an iOS/iPad app already in Apple's App Store; and it turns out that a working macOS/Mac (10.15 or later) app can be built from the same project, with no code changes, by simply checking the Mac (Catalyst) checkbox in the Xcode (11.4 or later) project.
What is the proper sequence of setting the correct bundle ID for the Mac app, getting any new provisioning profiles (if needed), adding anything else required to the Xcode project (Credits?), adding to the iTunes Connect record for the app (description, screen shots?), etc., that is required to successfully upload the Mac app archive to the App Store, so that customers who download or buy the iOS app can get the Mac (Catalyst) version as well?
Are there any features or functions that need to be added or removed from an previously approved iOS app to prevent the macOS version from being immediately rejected for being unsuitable as a Mac app? (and not including any reasons that might cause a new build of the iOS app to be rejected as well.)
Have noticed a weird forced upgrade issue with TestFlight. Opening the app and it shows the Welcome to TestFlight intro screen, and pressing Continue shows an alert with the message:
TestFlight Unavailable
We've release a new version of
TestFlight. Download the update in the
App Store to continue testing.
However, opening the App Store, the latest version appears to be already installed (shows the Open button).
This is on iOS 10.3.3
I've run into this before, looks like TestFlight isn't auto updating from the app store. Was able to get it working again by uninstalling and re-installing TestFlight from the app store.
Hope this helps
I had built an app which is already available in the app store with version 1.0. This app has local database (i.e. SQLite). Now I am working on next Version (i.e 1.1) and in this Version I have added a new table to my local DB. With this the development is complete.
Now, using testFlight I am performing Internal Testing.
Let's consider two Scenarios:
Case 1:
On my device, I had freshly installed the beta build version 1.1 from testFlight. Once installed, I checked my local DB and found that my local DB is updated with the newly added table.
So this is working fine.
Case 2:
Let's consider a scenario Wherein on my device I am running my app store build i.e version 1.0 and now I am installing the beta build from Testflight. Once clicked on install button I get a message "Do you want to update the existing app" and by clicking on the ok button the beta build which is version 1.1 is installed on the app.
But when I checked my local DB I found that the database is not updated with the new table. i.e. It's still showing the older database into the app.
Why only my local database is not updated in the second scenario?
Does testFlight build do not override complete app store build along with local DB?
If you want to really test migration process on production you have to install your app with Itunes because TestFlight or the build process via xCode does not completely override the App.
Install an ad hoc distribution of an archived build of the update using iTunes on a device that already has the old version of the app installed.
Test your App with Itunes
I had similar issue with CoreData. I had to make a migration of my DB, and I was unable to test the real scenario of updating the App.
The only true test was :
Have the old app (from the actual store) installed on the phone.
Install your new App with Itunes with an Ad-hoc distribution.
I have a build installed from TestFlight on ios device. I am not able to open this app. I have not accepted the invite for next version. Does INSTALLED build get invalidate after new version is released from TestFlight? What is the behaviour for Internal and external testers in this case?
We have had a number of our app's TestFlight users report that after updating iOS they can't open the app. We had to send them a new build to get things working.