A user sent me a screenshot saying that my app no longer works for him when he is offline. It's an alert screen from the App Store indicating that "In order to access the App Store, you have to turn off airplane mode or enable WiFi".
This screen instantly appears over my app when he opens it. The app does use in-app purchases but it is a very old Objective-C based app.
I wasn't able to find any information on how I might eliminate this problem 😔 and would appreciate any hints.
Related
I want to release an update of my app with the new addition of an app clip. Apple states in their documentation
Safari's Smart App Banner and sharing via Messages is only available when the app clip is published in the App Store.
Is there any way to verify that the app clip via smart banner will definitely work once the update is available in the store? Otherwise I basically have to hope that everything was set up correctly which I just refuse to believe that's the case. Did anyone do this yet and can tell me how to verify everything will work as expected?
I added Apple App Clip but later removed it not yet needed. It was added "Advanced App Clip Experience", later deactivated, but when you bring the NFC tag to the phone, an alert still pops up with an empty content and message "This app clip is not currently available in your country or region".
Deactivated Advanced app clip in App Store Connect
Expired all builds in TestFlight, which contain App Clips
Everything in app association file, domains for app clips, etc - removed
So why NFC scanning still present App Clip, but not redirect me in app/safari as earlier?
I had the same problem. The fix was to ensure that the App Clip Experience was deactivated in App Store Connect.
I submitted a binary/build that contained an App Clip to Testflight so that I could access the Advance App Clip settings.
Deactivated the App Clip Experience (your step #1)
Waited a day to account for the caching system, and now, after testing, scanning my QR Code (in your case, it would be triggering the event with the NFC tag) produces the correct results.
It is important to note that even though you may have a live app that does not contain an App Clip, you must still deactivate it in Advance App Clip.
I have submitted an app on Appstore.
The app got rejected and here is the Apple Response
"We discovered one or more bugs in your app when reviewed on iPhone running iOS 9.3.1 on both Wi-Fi and cellular networks.
Specifically, the app loads indefinitely upon launch. Please see the attached screenshots for additional details."
I have tested it in multiple ways as told by Apple but unable to reproduce the issue. Moreover Apple says it "the app loads indefinitely upon launch" well the screen shot they have send is not of launch screen but that is of a view controller which comes after launch screen.
Please guide me to overcome this issue.
It sounds like the tester was confused by the contents of the post-launch view controller. You should provide some guidance to the user on how to use the app once it launches with no data. For example, you might have a UILabel that appears to new users explaining how to start using the app. Effective user onboarding is practically a whole discipline. You can seem some good (and entertaining) analyses of user onboarding processes at https://www.useronboard.com/
I'm in the middle of getting my very first iOS app pushed out and have been having some trouble with the review process. The app itself is good, but it was recently rejected as Metadata Rejected for the following reason:
Your iTunes Connect settings indicate that your app serves
advertisements. However, we were unable to locate ads in your app.
The thing though is that when I run the app on simulators and my test device (an iPhone 4S), the test ads are coming through fine and are consistently located on the bottom of each screen. I've made sure to include the iAd framework in the binary and have signed/agreed to the iAd contract, but when I asked for more information, all I got for a response was
Your app is metadata rejected as we have asked where to locate ads in
your binary, as your app uses IDFA.
Has anyone else encountered something like this before? Is there a final step that I'm missing to have the real ads show up for the Reviewing process? All other topics close to this that I've found seem to refer to options that are no longer on iTunes Connect.
After sending them a screen capture showing the test ads being shown, it's suddenly been approved. How very odd...
I have an app that uses the ALAssets framework to access to the users photo library. I wrote some code that detects whether or not the app has permission to access the photo library, and if it doesn't, I display an alert message which tells the user to turn on location services for the app in settings.
Problem is, when the user manually changes the privacy settings and then they reopen the app, iOS forces the app to crash with SIGKILL.
I've noticed that the way another app handles this is by somehow detecting a change in the privacy settings, and forcing the app to restart the next time the user opens it. Does anyone know how to accomplish this?
You misunderstand what is happening. Your app is not crashing (though it may appear so if you are running the app with the debugger).
When you switch to the Settings app (and your app is suspended in the background) and change the privacy settings, suspended apps are terminated. When you switch back to your app, it is simply started again. This is no different than your app being killed for any other reason.
It is up to you to code your app to handle this by restoring its previous state. The other app you talk about is simply returning the user to the previous state. Many apps do this. It has nothing to do with being killed due to privacy changes. The app would restore state when being killed for any reason.
You can check whether you're authorized to access the photo library using the authorizationStatus class method of ALAssetsLibrary. You should check this value in some method that will be called each time your app "opens", and update your UI accordingly.