My app just got rejected, and the reason was that the Apple Watch Extension was "Booting to White Screen" on Apple Watch. They sent me a screencapture of Apple Watch screen that just has white screen. Not much information.
I honestly have no clue where I went wrong... seeing that the app runs fine on both iPhone and the Simulator.
I don't have an Apple Watch to test this with or any logs on real device to show you although I wish I could give as much information on this question.
I don't have any info I can supply other than the fact that they rejected the app, and app doesn't seem to run on real device.
I don't think it would be a code issue seeing that the First Screen in my app is just a few buttons for menu, without much things happening.
Could anyone give me any insight to how to approach this problem? or has anyone had a similar issue?
Here's the response from Apple.
2.2 Details
We discovered one or more bugs in your app when reviewed on iPhone
running iOS 8.2 on both Wi-Fi and cellular networks.
Specifically, upon review we found the Apple Watch app will boot to
white screen display upon launch.
Next Steps
Please run your app on a device to identify the issue(s), then revise
and resubmit your app for review.
For new apps, uninstall all previous versions of your app from a
device, then install and follow the steps to reproduce the issue(s).
For updates, install the new version as an update to the previous
version, then follow the steps to reproduce the issue(s).
If we misunderstood the intended behavior of your app, please reply to
this message in the Resolution Center to provide information on how
these features were intended to work.
Just in case anyone is wondering or having the same issue... it was really a stupid mistake.
I didn't put the images used for Apple Watch in the correct asset catalog with correct target membership. That's why it was displaying the images correctly on simulator, but not on real Apple Watch, since images weren't embedded within the app.
These kind of things needs to be double-triple checked before submitted to app store because it doesn't show on the simulator.
Related
I had completed a Flutter app, which seems to work well in simulator. I then went on to release the initial version of the app to AppStore Connect and sent it to beta testers via TestFlight and they were able to test it without any issue and sent me some feedback.
I made a few changes to the app based on the feedback (nothing too drastic) and tested it throughly in the simulator which seems to work fine. But now when the users download the app via TestFlight it crashed while opening and I cant seem to fix it no matter what I try. Any help would be really appreciated
So far I have tried,
Followed this article letter to letter
Modify optimisation parameters in Build Settings as mentioned here
Tried this SO answer
Crash report from XCode is not much of use since it is not very readable (as attached in the picture).
Can't yet seem to find any reliable answer, Any help on this would be much appreciated.
I created a app that has a AppClip which will pull up a restaurant menu. The invocation URL is similar to "www.mydomain.com/restaurant/113", this will be launched via QR code.
I tested the AppClip on both Xcode build and TestFlight, also tested with AppClip local experience which all works fine on my device.
Basically I follow these 2 docs when testing the Clip. link 1 , link 2
However when I submit the app to AppStore, I got rejection with the reason of "We tried again however we continue to see only the progress indicator clip was launched."
The review team wouldn't provide more information on how they launch the clip and how I could reproduce this issue. I couldn't reproduce this locally either following the AppClip test guide. if anyone have seen similar issue I appreciate your help.
Apple suddenly approved the exact build without replying anything. So I guess it's a issue on their side.
Recently I submitted my App to App Store for review and get a rejection which says my App is loading forever:
Guideline 2.1 - Performance - App Completeness
We discovered one or more bugs in your app when reviewed on iPhone and
iPad running iOS 12 on Wi-Fi.
Specifically, the activity indicator spun indefinitely on launch, then
no further action was generated at the time of review.
Next Steps
To resolve this issue, please run your app on a device to identify any
issues, then revise and resubmit your app for review.
If we misunderstood the intended behavior of your app, please reply to
this message in Resolution Center to provide information on how these
features were intended to work.
For new apps, uninstall all previous versions of your app from a
device, then install and follow the steps to reproduce the issue. For
updates, install the new version as an update to the previous version,
then follow the steps to reproduce the issue.
Resources
For information about testing your app and preparing it for review,
please see Technical Note TN2431: App Testing Guide.
For a networking overview, please review About Networking. For a more
specific overview of App Review’s IPv6 requirements, please review the
IPv6 and App Review discussion on the Apple Developer Forum.
Please see attached screenshot for details.
Before I submit for review, I have tested it on simulators and real devices, both takes 5-10 seconds to open.
I am using Firebase and Ionic, can someone give me some suggestions, what caused this issue? I google searched that Firebase supports IPv6 and now I have no clue why the issue occurred.
There's no hardcoded IP in the source, the only URL I am using is querying rates from Canada Post by url: 'https://ct.soa-gw.canadapost.ca/rs/ship/price'
Any help is appreciated.
We are having the same kind of report from Apple despite the fact we are testing on 6 different devices, iOS 11, 12, 12.1 with or without network.
We are also getting no issues from our beta testers.
As far as I can tell, on the Launchscreen we are spending about 6 seconds (iPhoneX) waiting for Metal to launch. There is nothing else in our log until our first VC hits its viewDidLoad.
We had the same kind of report two weeks ago with a very different iteration of our app, on resubmission the app went through
Now we have tightened up a lot of app behaviour and been rejected for the same reason multiple times
Its frustrating because of the lack of supporting information from Apple, such as logs.
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/
A user has reported that my app suddenly won't launch on their device. They sent me a video, and they launch the app, the launch image screen shows for a split second, but then crashes back to the iOS home screen.
The user tried deleting and reinstalling the app with no benefit.
I use Crashlytics, and am not getting any reports of crashes from them (or any other user- although I've seen them in prior versions so I know it's working correctly). I'm also not seeing any crashes in iTunes connect.
I asked the user to send me any crash reports in the Settings Diagnostics section and they said there are none listed for my app.
I have confirmed that their iOS version is supported by my app. (iOS 8.4).
I'm not sure where to go next, and would appreciate any pointers. Sorry for the vague question but I have posted everything that I know about the situation.
Just wanted to provide some closure on this. The user ended up wiping and restoring their device, and it solved the problem. It seems extreme to me but it was their own suggestion and didn't take them long to do. So I'm not sure what caused this but that's one (albeit brute force) way to fix it.