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.
Related
I've made an app (called BeSharp), tested it a lot, uploaded it to Apple AppStore, and now all users report that the pop-up menu I use (custom one) does not respond to clicks.
It does not crash, so I don't understand how to get some debugging done.
So, the question:
How can I debug release version?
Thanks in advance.
P.S. Please find below some promo-codes if you wish to test an app yourself:
FAYNW9XTTMPY
LYK7EYJYJM4E
T6FW34E4TL6J
NJ99R4E39WEW
PJ473MERJKTH
MK4EMXE9XFFW
LN7AFXHJN9YK
MTTKW4PMXPFP
KK9HE74MKFJL
X6PWPHERHMLF
E7P96NNNAAN6
N93FFTPPA366
T9JX6PMN9ELT
JP39XKTT4J6N
Y3Y4R643E6F3
33HWLF4PFJPA
7XYW7NAH7A63
JNP4EYJHKLN6
46KPNPYFYALJ
Thanks everybody for comments.
I solved the issue.
After inserting some NSLog into code, and running release version on real device, I have pinpointed the issue, and it was in custom button component - in 6.1 some Alpha test function works incorrectly.
So I just updated it and everything worked fine.
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).
Some say it doesnt start on their HTC Hero, another says it doesnt open in their Cliq, etc. I built the entire app using my Droid X to debug. Now that the app is released, and the code is interacting with so many different types of hardware, how do I figure out what may be going wrong for these users?
In my Crash errors log I have one record of a crash, and I believe I've already fixed this. It was certainly not responsible for the crashes that users are complaining about.
Maybe you have to check manually or maybe it's a problem of multiresolution because different mobile have different resolutions. Otherwise if it is possible then you have to include crash log report in your application which send crash logs to your email id.
Or you can ask them to install crash log reporter and set your emailid to target for crash report. Try this link, first one for manually adding code to your application.
https://github.com/tomquist/Android-Error-Reporter
http://www.androidzoom.com/android_applications/tools/log-collector_tlt.html
Do you have any Logcat outputs in release mode? May be they help you out..
Alternatively, you can test it out on 3rd party mobile testing vendors.. Where in you can buy some hours and do some quick testing...
I'm trying to send push notifications to an app. The program, PushMeBaby, which a co-worker of mine used does not seem to work anymore. I get an -909 error from the SSLwrite command. I couldn't figure out the meaning of it.
Does anyone know a good tool/program that sends push notifications to the APNs-server?
or has anyone know, what the error code means?
Yours
Bujtor
Well... as it turns out the problem was the certificate.
Apparently it's not that easy to get the correct and valid push-certificate. My boss's third attempt succeeded. The Certificate Signing Request had to be made using the MAC i'm working on, where PushMeBaby is running. Otherwise there was no private key associated with the certificate. In addition the provisioning profil had to be made to only work for that one application.
I hope it helps others having the same problem.
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.