I have a strange problem with my app. I have finished the design and I am ready to update it on the store however, when I do that and I test my app using test flight the app is completely different from the version installed from xcode.
Some colors are different the are bugs that are not present when testing it on xcode and even the status bar that I have hidden is now visible..
I have other apps on the store and i never experienced this isuues and I am sure that I am uploading them right version of their app..
What could be going wrong?
Related
Apple have rejected my React Native app for external beta testing because:
when reviewed on iPad running iOS 11.2.5 on Wi-Fi connected to an IPv6
network….the app launches to a white screen and no content is loaded.
After some weeks of back and forth, they’ve admitted that it was not related to IPV6, and have given me some further info:
The app’s initial React Native view controller loads with no defined
‘loadingView’ or ‘contentView’ elements. It appears that there is code
in place for Javascript updating, but as stated, we’re not seeing any
attempt at the app to reach out - it appears likely something was
disconnected between the executable and associated bundle files
between your project and the submission.
I have not seen this issue when testing on my own devices or on the iOS Simulator. Even when submitting the app to TestFlight for internal beta testers, and then installing on my iPhone via the TestFlight iOS app, it always works fine. So, I'm baffled as to why Apple sees this and I don't, and I don't really know where to start with debugging it.
Okay, case closed, I think. And it was procedural issue rather than a technical one, down to my misunderstanding of Apple's process.
I only thought I'd ever submitted my builds for External Beta review. I hadn't intended to submit it for actual inclusion in the App Store just yet. But I think that's what I must have done, and that's the version that Apple have been referring to all along. They haven't actually been looking at my subsequent builds, where the problem was fixed, as a part of this process. That's because those builds were submitted as External Beta test builds, which is a different review process.
Apple clarified this to me by sending me screen shots of the TestFlight version of the app (all good) vs the App Store submission binary (blank screen). And the penny dropped.
I have an app that has been on the App Store for a few months now with about 6 previous updates that have gone very smoothly. I use Test Flight to test the app on my device before submitting. This time around everything looked fine on Test Flight as usual so I went ahead and submitted the app for review. It was approved and the status switched to ready for sale, however, when I tried to download the App from the App Store it said it was unable to downlaoad again with the options to try again or done. I have tried it on numerous devices and it appears to be a problem for everyone, not just myself. This happens even though the same build worked great with Test Flight. Can anybody help? A lot of people have failed to download or update their app and it is affecting us a lot.
Now, i understand that you have checked several devices and all got the same installation issue.
But i think, it is important for you to know,
You might face issue in installing app from App Store, with TestFlight build still installed in your device.
Please try uninstalling the Test Flight build first and then install app from App Store.
I was trying to test update scenario from live App Store app build to RC using TestFlight, but TestFlight gives me alert "You already have this app installed. Do you want to replace..." (see below screenshot). After confirmation, all data from App Store version is gone.
Steps I do:
Install live app from the App Store
Login and do some operations to get data in the app and Keychain
Go to TestFlight iOS app
Tap "Install" button in TestFlight -> alert "You already have this app installed" appears
If I tap choose Install, new build is installed
Result:
The app's content including Shared Container (data shared with Extensions) and Keychain are completely wiped when I open the app again
Edit: The alert in TestFlight appears with any app (I have tried multiple different apps from different dev accounts). The actual data deletion happens only for some.
My question:
Is this expected behaviour from TestFlight or is it any issue with my app? I'm not aware of any changes between versions which could cause any issues.
I believe this was not happening before (the last time I tried was few weeks ago).
I couldn't find any documentation or release notes regarding TestFlight app behaviour or changes.
Did anyone experience the same issue? Or do you know any resources describing this behaviour?
Thanks for any answers!
After long research, trials and errors, creating radar and releasing update to App Store, I have an answer:
Alert is there always and does not have relation to losing data.
The alert with warning about possible lose of data is being displayed always for any app being installed from TestFlight over the Non TestFlight Build.
This was true for any of multiple apps I have tried.
identifierForVendor changes when overwriting app with TestFlight build.
When you have App Store version of the app installed and overwrite it with build from TestFlight, result of [[UIDevice currentDevice] identifierForVendor] changes
This is unexpected since it is not mentioned in the documentation (see below)
In my case unexpected change of identifierForVendor was causing "loose of data" which wasn't actual lose of data, but it is happening only for TestFlight builds which you cannot debug, so it was hard to find the issue.
Documentation of [[UIDevice currentDevice] identifierForVendor] says:
The value in this property remains the same while the app (or another app from the same vendor) is installed on the iOS device. The value changes when the user deletes all of that vendor’s apps from the device and subsequently reinstalls one or more of them. The value can also change when installing test builds using Xcode or when installing an app on a device using ad-hoc distribution.
as per best of my knowledge,
if you have installed application from App Store (suppose of version number 1.0) on your device, and lets say your are again downloading/installing same app with same version number 1.0 from TestFlight, you will get above message.
This is because you are trying to install app with same version and bundle id that already does exists on device.Offcourse you will lose data/settings of app, as its replacing your app not updating.I also gone through this scenario.
If you have the full version of an app installed on your device and you install the same Beta App, your app data may be corrupted or lost and may not be recoverable. You should back up your information before installing a Beta App.
http://www.apple.com/legal/internet-services/itunes/testflight/sren/terms.html
I don't know how this happens
I have a serious issue which I cannot seem to solve.
Recently I have made an update to an IOS app, and when testing in XCODE as both Ad-Hoc, Debug, and installing via the .IPA on a device the issue cannot be replicated. However when I download the app from the App Store, it crashes.
Does anyone know how this could happen, and any potential solutions? I am getting lots of complaints from users, and not sure what to do?
Could part of the binary upload have got corrupted?
Probably you always compiled your app in debug mode. But when sent to App Store you made a release compile. click the arrow in the run button select scheme and chose "release mode" and run your app it will probably crash.
check if you used NSParameterAssert as they are not called in release mode
I cannot say why your live App Store application is crashing and the debug version is not. Two possible solutions:
Crash reports:
To find out why your application crashed, you might want to check if there are any crash reports available on iTunes Connect. Log in on iTunes Connect and click on your application. Scroll down to Crash Reports. You will find out more about why your application is crashing here.
More information about crash reports here at Apple's own iOS Developer Library.
Prerelease your app with TestFlight: For in the future: test your application by uploading it on iTunes Connect and testing it with TestFlight first before submitting the application to the iTunes Store. This will save you a lot of (review) time if you find a error.
I realize this is an old thread but I had the same issue with my App that I released. Meaning it worked fine in testing, but when I released it it would crash. The culprit ended up being the fact that I am using In App Purchases. I have two items that can be "bought" but I had only enabled one of them. In testing it was able to read both of them, but with the release version, it was only pulling the one that was enabled down, creating the crash. The fix was simply enabling the disabled item. I didn't even have to redistribute the app, though I had to wait for it to "percolate" through... Anyway this may help someone in the future.
Check if your app is looking for too many IAPs.
I just had this problem and my problem was I had deleted an IAP from the App Store, but didn't remove it from the app code.
For some reason it only crashed when downloaded; I used a promo code to do this before launching my app.
Thanks to Tornado for the inspiration to try this variation.
Ive submitted my first app and it has been approved. But I have a few issues that i'd like to ask what I should do about.
One of my images/icons that I have in my app showed correctly in my distributed binary at my end (running it in debug simulator from xcode) but on the app downloaded from the app store it is not showing at all?
IPads cannot see my app in their search of the app store?
IOS 4 is needed to run my app. How do i change it so that it can be run on IOS 3 aswell? And if i make it IOS 3 compatible does this mean that it cannot be run in the background at all (i.e. when the close out of my app and go back into it will it restart the entire app)
Also does anyone know whether submitting an update is quicker in the review process than submitting a entirely new app?
Thanks in advance for your help
Thats a QA issue. The simulator is just that and if you want to be sure that your App runs as you expect on hardware then you need to check it on hardware. There are instances of images that decode on simulator but not on hardware.
iPad only runs iOS 3.2 at the mo so if your app runs on 4.0 it wont show up for iPad.
See 2 and no you dont have multitasking in 3.2 so you need to make sure your app state persists across atomic launches. You'll need to remove/conditionally compile any 4.0 only API in your App. If thats a problem wait until November-ish.
Maybe, depends, probably no. Lead time on update/new submission is around 8 days +/- YMMV.