When I install my app through Xcode, App Store no longer recognizes that the app is installed. This makes things like deep links difficult to test.
I have verified that my Product Bundle Identifier is the same for Debug and Release (it's different for AdHoc, but that shouldn't matter in this case). When downloading from App Store, it does not add a second app, it simply updates the previous app.
Related
So I have successfully implemented universal linking in our React-native project.
It correctly links to the right page in the app with the parameters provided.
However, when we are testing it on testflight our testpeople have to restart their iPhone or delete and reinstall their app in order for it to work.
Will this work differently when the app is uploaded to the appstore? I'd have hoped that the certificate is downloaded upon updating the app but as our tests in testflight shows, that doesn't happen. The documentation is very thin on this topic.
It would not be ideal if we have to ask all of our costumers to reinstall the app or reboot the phone in order to use our new feature.
I'm trying to install my app from TestFlight.
When I press INSTALL, the download indicator runs for a sec and then stops.
I can see the app on my phone, clicking on the app raises
Unable to install the app, please try again later.
It's very weird, since I run the app on a physical device using Xcode, and everything was just fine. Also, older versions of the app are downloaded from TestFlight without any problem.
The app passed through all checks before uploading to the store.
How is it possible that I cannot install the app from TestFight?
What can I do in order to debug this issue?
This can be happen with number of reasons as given below:
Might be you are using the developer profile instead of Adhoc profile
OR using an app identifier that is different from the one that belongs to your profile
OR might be an issue in enable/disable of iCloud and Gamecenter
What you can do is you can connect the device to PC/Mac. Open the iPhone Configuration Utility and see the logs after you press install from the build in TestFlight. It will helps you to dig it.
And last hope is this issue can be at apple side as many developer are facing as given below: https://developer.apple.com/forums/thread/26759
It's not the correct answer.
In case you are in a rash, and your project was already uploaded from another Mac to the store, a temporary solution will be to import the project to a well-configured Xcode from another computer and send it configured back to your computer. Make sure you have all necessary certificates, Build, and upload to the store. Then I was able to run the app on TestFlight and upload new updates without problems.
IMO, Apple did a really bad job connecting and configuring Xcode projects to the store. As a Flutter developer, I upload apps for both App Store and Play Store, and working with Apple is frustrating. There were no logs or indications about this issue, and it's almost impossible to track the mistake.
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.)
Is it normal that TestFlight uses a different keychain then the app store build?
I have added my login-credentials in my keychain so that the app login's automatically when it is started, but when I install the TestFlight app over the AppStore app.
The keychain seems to not be the same as the app store because it cannot find the credentials.
both apps have the same bundle identifier.
Yes it is normal. As you install your app from AppStore and from TestFlight, iPhone/iPad consider both the app as different apps even with the same name. There may be difference in both builds'versions. Or even if both the builds are same it consider the different one. If you have noticed the TestFlight version and AppStore version are installed separately. And another thing to note is that when you install an app from test flight then the app name Start with a colored Dot which denotes that the build is downloaded from test flight and it makes the app different from other all apps.Please see the Image attached which show a build installed from test flight.Application installed from TestFlight denoted with colored note in the starting of the application name
I have an app on the App Store and I downloaded it onto my phone. Now, I want to integrate iCloud and Push Notification into this app. If I open Xcode and run it on the same device, it overwrites the App Store app. My goal is to have 2 versions of this 1 app on my phone: 1 from the App Store and 1 from Xcode for development purposes.
I have read two articles and can't come up with a solution:
Unable to install same apps on 1 device
Create Multiple Targets/Apps for 1 Xcode Project
By changing the Bundle Identifier, it is possible based on the article above. But will there be a problem when testing iCloud and push notifications? The App ID and what is in iTunes Connect relies on the Bindle Identifier and when testing iCloud and push notifications, I need iTunes Connect. So this is the problem from what I see.
Any suggestions?
Create a new bundle ID (say with an added .CLONE suffix). Use Xcode to build your App Store submitted code (from your source repository) identical except built using this new bundle ID. Install it side-by-side with the original App Store app (identical source code).
Then manually copy your notes out of your App Store app and paste them into the new Clone app. You can use Xcode to back up the new clone app's sandbox. (There might also be tools that are able to pull you app's notes DB out of an unencrypted iTunes backup, if you make or have such.)
Then delete your App Store app (if needed) and install any new version as needed for development and testing using the original bundle ID for iCloud testing.
Your real non-test data will reside in the Clone of your earlier App Store app during development. You can copy it back into the App Store submission when done.