I've run into a funny problem. Our app, which was working prior to Saturday, can't connect to the server to get the necessary data. The server is fine, everything is up and running and I have rebooted it. The Support Tech has said the same. So it points to either the code having something that didn't change, or the ip/database info changed and the code is using the old info; as far as I know, we've changed nothing. Will I have to check the code?(I didn't write it, someone was hired to do it) or is there something else that could be causing the problem?
The error message:
"The app is currently unable to connect to the server. Please try again."
It's a very unspecific error message so I'm assuming the developers of the app put that specific message in themselves.
Assuming you have the app on an iPhone you may be able to diagnose (but not necessarily fix) this without getting into the code. Download Fiddler and use this tutorial to setup the iPhone so you can watch the network traffic. This will allow you to see exactly what requests the app is making to the server and you may be able to figure out the problem. Either your request isn't making it to the server or the server is returning an error message. Either way Fiddler should be able to give you that answer.
EDIT:
HTTP Scoop is a pretty easy to use client for the Mac that does what Fiddler does for PC. You can use it for free for 2 weeks so that should be enough to help you out.
Charles would also work. I know you can get a free trial for that as well.
Related
when I want to upload a new version of my apk after grab my app to upload it go fast to 60% .
and stacks and never continue
screen from console：
Sometimes it is caused by VPN or proxy of your computer. Please try
to disable VPN and proxy, and try again.
If you use company’s computer, sometimes some company policy will
wrongly block some uploading. Normally your computer will popup a message to tell you about it. Pls carefully check if there is any message when
you are uploading.
Normally Huawei AGC will check if the package name of the uploading
app is used. It will take a while(had better waiting for 2 minutes).
After the checking, AGC will tell you the result.
Try to use different browsers to try(it’s better to clear cache of
the browser) or reboot your computer.
If you still have the issue, please catch video or screenshots, I
will deeply appreciate it and research it.
You are advised to clear the browser log and upload it again.
If the problem persists, Please provide the error screenshot and browser logs, According to this we can analyze your problem and try to help.
I'm planning to release a new app in the future.
I have a custom logging function which logs some application data (not crashes) into a file (location manager state, app foreground-background transitions, main actions...). These logs helped me a lot to debug problems which were app-related, but not causing a crash. Until now these were in the documents directory (shared in iTunes) and the testers sent them to me after they saw some incorrect behaviors, however I don't want to share them anymore because this directory contains the app's database too.
I'd like to obtain these logs even when the app will be on App Store, but I don't know how this should be done. As I wrote, it is a new app and even after the test phase may exist minor bugs. I know that the users can report problems in iTunes or on the Dev site, but without a detailed scenario or log it is really hard to correct a bug. Should I make some kind of in-app bug report functionality (even if this creates a wrong user impression) ? How is this usually handled ?
Edit1 : I'd want these logs only if the user thinks something went wrong and should be analyzed, otherwise I don't really need them. I think some kind of user action is needed to confirm that something isn't working as intended, that's why I asked about making a functionality ( like the "Report a problem" in the Maps App ).
Thanks
If your app is gonna crash, don't submit it to AppStore because more likely it will be refused.
I don't know your app but usually logging slow down things. But if you really want logging I would suggest you to first find out if application crashed. For instance in your appDelegate when the app is terminated without problems set some NSUserDefaults value like closedSuccesfully=YES. Just after you start app set closedSuccesfully=NO, but if it was set to NO before it means your app crashed last time. In that case you could grab your previous logs and try to send them to your server via http post message. On your server there might be very simple php script to get that data. That way it will be automated and your users wouldn't have to do anything and you would get all crashes even these not reported.
I am writing a caldav server for our company which will be compatible with a number of clients, one of the key supported devices will be iPhone running iOS 4+.
This server will only support VEVENTs however when the server is initially configured under settings in the iPhone, the iPhone thinks that the server also supports VTODOs. As there is no VTODO calendar outlined, it then proceeds to try to create a default one on my server. The Warning in the console output reads: “This account is enabled for tasks, but has no task calendar. We’re going to create a default one” I return that MKCALENDAR request with an empty response with 403 status, however the phone doesn’t seem to realise it’s failed and still puts the Reminder list in the Reminders app. I’m not where I should be flagging to the phone that this account is not enabled for tasks.
I haven’t been able to find much information on caldav servers in general and none on what iOS supports and is expecting from a server. I have been adhering to the standards in multiple RFCs including 4791, 5545, 3744 and 4918 but have not been able to find any help for this particular issue. I have also looked through the developer resources provided by apple to no avail.
Any help or pointing in the right direction would be greatly appreciated.
Jo
We needed to support serving iCalendar events to iOS as well, and struggled with some of these issues. For our problem, the calendar was read-only to our target clients (which I'm guessing is likely not true for yours). The server task was dramatically simplified when we realized we could use the subscribed calendars option to just get a calendar feed without anything else:
Not exactly a direct answer to your problem, but hopefully useful as an option to consider.
Some users reported there are bugs when run my app on their device.
Is it there a way to get the crash log that occurs on users' device?
Or is there any solution to catch all crash log for cocoa touch?
Welcome any comment
If you want to reduce the amount of effort users need to go to, something like PLCrashReporter is quite good (I remember seeing a handy wrapper around it recently but I lost the URL).
The most common chrash logs are available through itunesconnect.
Also, the crash logs get synchronized to the Mac or PC. Maybe not the latest news, but this link should get you going: http://aplus.rs/apple/how-to-find-crash-logs-for-iphone-applications-on-mac-vista-and-xp/
You can check out apphance (http://apphance.com). It provides remote access to a test user device including logs written by developer, crash logs and more....
Disclaimer : I am CTO of company which created apphance and co-creator of it.
I use QuincyKit and really like it. It's free, and easy to install on your server.
If you want a hosted solution, I have heard a lot of praises for Crashlytics.com, but did not personally tested it (commercial product).
And forget iTunes Connect if you care about fixing all crashes. Often, you won't see crash happening in there (might be because users do not sync and many other reasons).
If been looking around the web and can't seem to find any good solutions to sending allowing your user to submit bug reports from your iPhone app.
How do you handle crashes and exceptions?
Do you send the error user-data to a server,
grab a log file from somewhere and attach,
or do you ignore it and pretend it never happened?
Anybody got any experience with this?
Update
I am aware of how to prepare you software testing it with Static Analysis, Leak Detection, User Testing etc.
But errors might still happen when a user (mis)using my software. Always assume your user is trying to break your software.
What I want to figure out is how (I, or rather the app) can provide me with useful data when/if errors happen. As they do even in top quality products – like my own ofc. :)
I'm looking anyone that has experience with allowing the use to send error reports, stack traces, logs etc. to see how they handle the problem.
Some people use built-in analytics like Flurry which will post exception data to Flurry's website which you can review later.
Also, Apple has a "crash log" reporting area on iTunes Connect, but I'm not sure if it works since I've yet to see something come through and I kinda doubt each and every person has run my apps flawlessly. Not saying I write poor code (hopefully), but not every device is created equal either so I have to imagine it has crashed at least ONCE. There's always the option of logging and sending to a server later though.
Most of the time though, if you give users your e-mail address within the app itself (like on an instructions or about screen), they will e-mail me about any issues. That's a little bit nicer since it gives you a chance to correct the issue before they hit the review forms on iTunes.
You can also try BugSense. It's free, realtime, error reporting for iOS
PS: I am one of the founders.
Crashes most of the time comes with problems of memory management. To test memory leaks and find in your code on to what areas you were leaking a memory. Use the Instruments if your using XCode.
In your XCode go to Run -> Run with performance tool -> Leaks.
You can check everything here when it comes to memory allocations.
Note: To avoid crashes, make sure you released objects correctly and check your scheduled timers as well.
Regards,
ZaldzBugz