i successfully created the .bar file and deployed in playbook simulator. i could see the icon of my application in the playbook simulator but when i click to open the application in playbook simulator it show a loading screen with white background and after a moment the player freezes without and error or warning. Did anyone faced the same problem and resolved the issue???? Please reply if anyone got the solution
That's an inadequate description of the problem. The "player freezes"... where? On the loading screen? After your main class displays? Between the two somehow?
Also, you can compile with debug mode enabled and deploy while running the debugger. Then you're very likely to see a traceback showing the specific error, instead of whatever this "freeze" is showing you.
Related
I have an app live on appstore. When I install the app in any device & open it by tapping on appIcon. It works perfectly, But when i open the app from appStore by tapping on Open button. App is launched but gets stuck on launch screen.
Launch screen does not go away & because of that I am unable to use the app. The issue is same in iOS-10 and iOS-11.
Here are possible solutions you can try out to resolve your issue :
First try to test your app in debug environment by adding exception break points & see if it generates any exception or not
Second thing is use crashlytics tool in your app so if any such issue occur when your app crashes or stuck due to exception than it
will automatically submit report to you. Its very effective tool.
Enable exception break points like this :
Edit:
If you still unable to get resolve the issue by above solutions than do 1 thing. From didFinishLunaching method comment all SDK
initialisations or any thing that you think could causing the issue
Now make a distribution build & upload to app store & do beta testing test flight
Once its make sure it works fine than you should uncomment 1 by 1 statements & get reach to the statement that causing the issue
Hope it will help you.
I have read some articles like app freeze with BKSendHIDEvent error:
iOS 9 App freeze with console log "BKSendHIDEvent", but my problem is slightly different from this one. Since I use ionic to build the ios app, I don't know how to trouble shoot the detailed error in xCode.
My problem is that when the app first runs within the xcode, everything works fine, but if I stop the debug and reopen the app from the simulator, no button responses at all. The whole app stucks at this stage.
I checked the simulator system log, it shows this:
BTW, when I kill the app(flick up the app) while it is still debugging, the xcode says this, I don't know if this was the issue:
I have also tried to get further information from the web inspector, but this does not response either. I could not reload the page by
window.location.reload();
There are no window object at all...:
So I'm totally lost here. I don't know how to further trouble shoot this error. Can anyone please point me to a correct direction? I have no idea why the web inspector shows nothing here and how to get the detailed error info in xCode.
Thanks in advance!
After several search, here is the fix:
App Freeze
But I still do not know how to trouble shoot, in the issues above, they mentioned race condition, how to debug this?
I'm using Unity Pro 4.5.3f3 + iOS Pro 4.x, Xcode 5.1.1, and tested with an iPhone 4S and 5 running iOS 7.1.2.
I recently took over development of an iOS app from a departing coworker at my game studio, and I'm attempting to compile the app in Xcode on my own machine for the first time. I have followed his instructions for which extra Obj-C code to add manually. The app works perfectly in Unity. Everything builds in Xcode without errors.
When the app runs, I see the custom splash screen loading as intended, but then the screen goes completely black. The app appears to be running fine...I can hear its sounds playing and it even responds when I tap the screen in areas where I know the buttons are supposed to be. There are no errors thrown to the log. But it doesn't display any graphics at all!
I suspect the Prime[31] plugin has something to do with it, as I get a strange log output saying Prime[31] didn't recognize several other plugins. And I can't delete it to test my theory, because way too many scripts depend on it.
Does anyone know how to fix this? I have lots of tasks to do for this app and I can't let something like this slow me down.
I encountered this issue last night when trying to configure my app to be compatible with Facebook Canvas.
Below is the line of code that was breaking:
FB.Canvas.SetAspectRatio(9,16, FBScreen.CenterHorizontal(), FBScreen.CenterVertical());
To fix my issue I surrounded the line with the UNITY_WEBPLAYER preprocessor directive like so:
#if UNITY_WEBPLAYER
FB.Canvas.SetAspectRatio(9,16, FBScreen.CenterHorizontal(), FBScreen.CenterVertical());
#endif
Doing this causes that line of code to only be compiled and run in the web player, and not on the mobile device. Hope that helps!
My iPhone application suddenly stopped launching in dev mode.
When I launch in simulator it pops up a dialog: SpringBoard failed to launch application with error: 5
There are tons of references on the web about error 3 and 7, but not the 5. I tried to follow the suggestions for the 3 and the 7, clean up the app, remove it from the simulator, restart the xcode etc... -- does not help. Can anybody shed some light about this mysterious error 5 and how to overcome it?
After a while the issue came back, so digging into it, revealed, that I must have accidentally turned on location simulation option in the Run configuration as well as Background fetch (launch due to background fetch event). I was playing with the background fetch and the location events, but decided not to use it after all. Turning those off in the run scheme brought my app back to live.
I got the same problem 2 hours ago then I closed the iOS simulator and Xcode then run it again it worked perfectly try it maybe it will work.
So, here is the answer. It's got something to do with the background location service. Apparently it was disabled for my application. Once I removed it from the Info.plist -- things started clicking again. Put it back -- the same exact issue. One would hope, the messages I got would be a bit more user friendly. Anyways, thanks for helping me.
Adding to dmitryame's answer, solving this issue for me was only accomplished by unchecking "Launch due to a background fetch event"only by Under Edit Scheme / Run Configuration.
Below is an image of the culprit causing the error message in my case:
Quit Simulator and clean Xcode. The fresh build will not show this Alert again. The possible reason for this might be switching between 64-bit simulator and 32-bit simulator.
As the title says, I'm having issues using LLDB. I've looked into this thread Xcode 4 hangs on attaching to (App name) when debugger is set to LLDB and followed the instructions given because I'm having exactly the same issue, and managed to debug by using GDB - it works flawlessly. Anyway, i'm working in a team and I'm the only one who's having this issue, so it's a bit annoying to switch back and forward from GDB to LLDB every time i commit changes so the workaround doesn't get synchronized in the remote repository.
I've checked the compiler, and it's set to LLVM 4.2. In fact, the app compiles perfectly and gets installed in the simulator (i can execute it once I kill and restart Xcode). I would try to reinstall Xcode, but it's a mess since it's a big-sized package and I have a limit on my internet usage, it would take a long while. Does anyone know what's happening here? Is it possible that LLGB is bundled outside XCode, even if I failed to locate it on the system?
Any insight would be appreciated. I can keep the workaround going, it's just that it's a bit annoying given my personal circumstances :-)
EDIT: More details about what I mean by 'hung'. I start with Xcode open, and simulator closed (it doesn't even appear on the Dock). I click 'Run', the simulator is launched successfully, and the application shows the Splash Screen. Then xcode shows the message: "Attaching to ". And now it's hung. You can close the simulator, and xcode is still attaching. Both the Run and Stop buttons stop working. You can try to exit the application by right-clicking on the dock, you get an alert message, and from this point you can't even type code: XCode is fully hung. The only choice here is to kill XCode by using Cmd+Alt+Esc.
This sounds like it could be the problem some folks were seeing in Why does the LLDB Debugger constantly fail to attach? where they'd modified their /etc/hosts file so when Xcode tried to connect to debugserver via "localhost", the connection was never set up.
When Xcode hangs, try switching to Simulator by clicking on its Dock icon. Don't use Cmd+Tab.
Upgrading to XCode 4.6.2 fixed this issue for me