Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
We have developed an iPad application and submited it to the apple store for review after properly testing at our end. Apple rejected our app giving the following reason:-
We found that your app failed to launch on iPad running iOS 5.0.1, on
both Wi-Fi and cellular networks
We encountered the issue when selecting the application on the Home
screen - the app displayed a launch image then quit unexpectedly. This
may be because iOS 5 uses a watchdog timer for applications; if an
application takes too long to complete its initial startup, the
operating system terminates the application.
For information about the watchdog timer, please see Technical Q&A:
Application does not crash when launched from debugger but crashes
when launched by user..
Another possibility could be a missing entitlement. For more
information, please see the Technical Note: Resolving "0x800003A",
applications not launching and "missing entitlement".
We are not able to understand why Apple has rejected the app since we are not able to reproduce this issue at our end, and Apple's feedback is not very descriptive.
So what can we do to workaround this problem and resubmit it to apple store?
When Apple tested your app, they tried to launch it, and it never finished launching. If it takes too long to launch (5-10 seconds) it will be terminated by springboard and never finish. That's likely what happened. It's also possible that you had bad entitlements, but you probably would have run into that problem sooner.
Is there any chance you're doing synchronous network access on the main thread when your app is launched? This could easily cause this problem. If so, you should fix your app to never do synchronous network access on the main thread.
you need to remove all the synchronous UI/WEB update calls which blocks applicationDidFinishLaunching:
to return YES;
applicationDidFinishLaunching must return asap without blocking application thread for lets say - 1 second.
move your blocking code to a method and use performSelector afterDelay for that.
Related
Closed. This question needs debugging details. It is not currently accepting answers.
Edit the question to include desired behavior, a specific problem or error, and the shortest code necessary to reproduce the problem. This will help others answer the question.
Closed 4 years ago.
Improve this question
I am currently writing an IOS app that uses Cloud Firestore as a database. One of the app's functions is a ticking down timer that needs to be shown on the screen for users to show how much time is left for a function. Problem is I am currently using a timer, but that doesn't work as when I exit the app it will stop updating the database on how much time is left . Any suggestions on how I could solve this problem?
There's no way you would be able to interact with your code while your app is closed. iOS is strict, once your app is closed, you have 30 seconds to process anything necessary. your app is suspended from regular activities,
As #matt mentioned:
A timer can run in the background only if both the following are true:
Your app for some other reason runs in the background. (Most apps
don't; most apps are suspended when they go into the background.) And:
The timer was running already when the app went into the background.
I also suggest a look over here:
Swift 3 - How to make timer work in background
Set a date and time in Database when the function for Timer is called.
You can then check whenever the app is open to calculate the amount of time taken.
In an iPhone app every time I end the phone call I want to ask user for yes/no type question & if 'Yes' is clicked the launch my application. I know I can get notifications for call end using CTTelephone but my question here is that is it possible to get the notifications even after my application is closed. If I run my application in background then there are chances that system closes it on low memory. Moreover apple doesn't support for continuos background application.
No, you will not get notification if your app is close. Since you app does not fall in one of the background modes you will not be able to run the app in the background.
In short, the functionality you want is not possible with the official Apple SDK and guidelines.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
I finish building my app and I don't see any error on xCode 4.2! Do I need to test it on the Instruments before send it to appStore?
You don't NEED to test your app although it would be nice for your users, instruments will let you see the performance of your app and also whether or not you have memory leakages.
Give it a go if you can Instruments.
I strongly recommend you to test your app on a real device before submitting it to the Apple Store because in various situations (depending on the size and complexity of your app) there are some errors or warnings that don't appear on the simulator but do appear on the real device. An example on this is the Media Player (this post is an example).
Another important reason is that the simulator does not support all real device situations. For example you can not receive Text Messages (SMS) or incoming calls on the simulator, and it is important that you test your app for such situations (handle states of appWillResignActive, appDidBecomeActive...).
And as our friends noted above, it would be nice for you to see your app in the way your customers will see it before you sell it to them.
It's not mandatory, but I'd recommend it - particularly if you were an indie developer looking to start making your mark on the Appstore.
Any warnings that Xcode presents are also acceptable - but anything serious that occurs during runtime and through the things Apple will do to it during the submission process will be flagged to you; you'll even get a crash log. (again, as a rule of thumb I'd recommend clearing warnings where possible - and given any time restraints on the project)
Just remember that no matter how much testing Apple will do - their systems can and DO miss things, like specific configs or situations on iDevices that just happen. (just because iDevices are very less fragmented in comparison to say Android, things always occur!)
Hope this helps - good luck!
Also, you might find this useful:
http://www.raywenderlich.com/2696/how-to-debug-memory-leaks-with-xcode-and-instruments-tutorial
Instruments is for performance analysis and is not necessarily a "part" of your app building process. It would be nice for you to do some profiling for your app using this tool so that you, as the developer, give the best UX to the end user.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Questions concerning problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.
Closed 9 years ago.
Improve this question
I want to develop an iPhone callerID application. I have following challenges to develop
How to detect incoming call?
Need to start my app when an incoming call occurs
Please help me out..I am new to iPhone development.
Thanks,
Srikanth
You can't do this. iOS apps cannot launch themselves without direct user interaction, and incoming calls suspend any apps that are already running.
I'm fairly certain this would be impossible in the iOS framework. Incoming calls suspend any active application and take priority over other operations. Further more even if you did manage the overwrite the iOS app lifecycle I think it is highly unlikely that Apple would approve the application because it attempts to replicate the functionality of the Phone app's caller ID. Apple doesn't like it when you try to replace their products (Ask Google Voice). They may have started to loosen up a little on this (See Opera browser and Skype apps) but I think this one would get flagged and rejected.
Short answer: you can't.
Apps are started when a user requests it, so you can't tell an app to start when a call comes in.
And an already running app is suspended when a call comes in. You can't pick up any detail about the call.
No. Simply you cannot do that. There is no public API is available to do that. Your app will be in sandbox environment and your app will be suspended when a call comes in. You cannot access them in anyway.
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 11 years ago.
Improve this question
My application hangs. Pressing the home button doesn't return to the springboard anymore. Additionally pressing the power button for 10 seconds doesn't turn the iphone off at all.
Is there any way to force a shutdown?
1 - To 'Force Quit' an iPhone application, hold down the Home button for up to 5 seconds.
2 - To force a reset (in rare occassions when 1 does not work), hold down the Power and Home buttons together for 10 seconds.
(this is documented in a Apple Support article - http://support.apple.com/kb/HT1430)
To force shutdown the iPhone 3G, just press down the power button first, followed by the home button. Hold the 2 buttons down until your screen changes.
That's it... A simple, but undocumented solution. Oh well. So far my iPhone has crashed in a few ways and this worked all the time.
If your application reproducibly hangs the phone, please file a bug report at bugreport.apple.com and attach a copy of your application. This is something Apple would be very interested in debugging. Thanks!
My iPhone hanged during boot when it tried to reset & erase all the iphoe contents.
Following are the steps to get your iPhone booting in Recovery Mode:
Step 1: Before getting the iphone in recovery mode, Open iTunes on your MAC or PC & attach the cable to iPhone.
Step 2: Hold down the Power & Home buttom simultaneously until the screen changes (around 10 secs.).
Step 3: Release the Power Button and keep pressing the Home Button for at least 30 secs.
Folow the instructions on your iTunes to restore the firmware of iPhone.
Hope, that this solution works for all who had problems like me.
Thankfully my problem is Solved.