So I finally got through the mess of preparing my app binary to support the iPad, making it a univeral app, and then I got this strange error "Missing Screenshot". And due to the fact that I hadn't uploaded my iPad screenshots to the original binary (I forgot) that error made sense. So I went into the original iPhone app, added my iPad screenshots, and hoped that somehow it would just work, but it didn't.
So then, I rejected the binary, and made sure the iPad screenshots were where they needed to be, re-uploaded a new binary, and it still says MISSING SCREENSHOT. I emailed apple, and they characteristically won't get back to me till probably sometime next week, so I am hoping that someone here can shed some on this error for me! What can I do to get that error to go away, so I can get my ap reviewed and updated? Thank you very much!
You need to set screenshots for all of the locales you are posting your app in
After you upload the screenshots for the new supported device type through iTunesConnect, the state will /should/ automatically change back to "Wait for review".
Related
My App is approved, but the updated version is not showing in the AppStore and in iTunes. It is still showing previous version(1.1). Can any one knows why this happens?
I too faced the same issue recently..
I requested the apple to fix my issue.
i received the responce as follows
However, as you've discovered, this process can sometimes take up to 24 hours to fully take effect. As such, I thank you for your patience.
Our latest app was rejected by giving following reason
"when the user launches the app, a blank black screen is produced"
We had tested this many times and did not notice this issue. We tested again now, but it is working properly for us.
Can someone help us to find out the issue?
I don't think anyone can help you find this issue, My suggestion would be to follow up with the Review Team and try to obtain as much information as you can from them. Such as, what device was it tested on, what OS version and so forth.
Ah, the many woes of the app store process.
Make sure that you have tested your app not only on the simulator but also on a physical device.
Secondly the issue might be that you have made some (false) assumptions about the data on the device, that you might have put there manually, but isn't handled when installing anew.
Therefore a plan of attack might be to remove the application complete from both device and simulator and try running them from a fresh install rather than on top of an already installed installation.
Best of luck!
Try to build and install your app from a clean state. You may not be seeing the same as the reviewer, because if you only "build&run" all the time, old files, which are not part of the final build, are still present on your device or in the simulator.
So clean the build folder, remove the app from your device, and try again. Also, check if you app can live without an internet connection.
Your best bet is to discuss this directly with the Apple guys (Resolution Center).
I already have asked about how to test Push notification in iPhone.
Now I have to test the same in iPad. I found that the tool PushMeBaby does not work in iPad. When I tried to do so it is showing some Socket error(5).
Is there any other tool which helps me to test this? Or Can I fix this error in PushMeBaby tool and make it workable to test the same in iPad?
Thanks in advance.
I am adding this answer just for those who may do the same mistake I have done.
It was giving me error sometime otherwise it was neither giving any error nor any push message is displayed. The Problem was in Device Token. Since I did not copy/paste it but added it manually it was very difficult to find the miss characters. When I replaced it with copy/paste data and re-execute it, it is sending a push message for each click.
Those who believe that PushMeBaby tool is only for iPhone/iPod are wrong (including me before today). It is meant for all the devices. Hats Off to PushMeBaby.
I found this information on a blog which talks about invalid product ids.
http://troybrant.net/blog/2010/01/invalid-product-ids/
I tried everything suggested in the
Apple forums and here, and still
couldn’t get it to work. Found the
solution – your app needs to be
transferred by Xcode for the sandbox
to be enabled.
Obvious, right? Well, if you are
working with an update to an existing
account, the device will still treat
it as an App Store-installed app.
Delete it, then transfer it again. It should work now :)
i am also getting invalid product ids.i am not able to get clear in the above said point...
i am not able to understand what i need to do when transferring the application into device...
Kindly guide me out and thanks for your help
That point just means that you need to run the app from Xcode in order for the sandbox to be available. (Build and Run)
Invalid product ids are a major pain to debug. If you're sure you've gotten everything on that checklist, then you just need to wait. Then only other problem that I've seen is that you might need to remove the app from the device and redeploy in order to get good products back from the store.
I had trouble getting the app store to recognize my sandbox test account. I had to log out wit iTunes, sync, then log in again with iTunes. Just using the device itself to log in/out didn't help.
When I tried to upload a build on device it give the following error.
Your mobile device has encountered an unexpected error (0xE8000001)
I am unable to solve this problem. Can anyone tell me why this is happening?
Anytime i get an unexpected error i hard reboot my device by holding down the home and lock buttons until the apple logo appears. No idea what causes it, but the reboot usually fixes it.
This seems to be a bug that is puzzling many users. No idea what the error actually is, but on this forum people claim:
this error will require you to restore your iPhone/touch, either through Xcode's Organizer window or iTunes. No way around it".
This basically happens when there's a communications error between Xcode and the iPhone which leaves Xcode confused about the state the iPhone is in. (You can actually make it happen sometimes by unplugging the phone in the middle of installing a build.) As the error message's text suggests, turning the iPhone off and back on will usually clear the error. You may sometimes have to restart Xcode or even your whole Mac, but not often.
To all
The problem get solved. When I set provisioned profile of device. It works.
Thanks for your help & guideline.