Your mobile device has encountered an unexpected error(0xE800002E)
Try disconnecting and powering off the device;then power the device on and reconnect it.
I received these message so many times. How can I fix it?
Although you can see this error when you connect in XCode, it is not actually an Xcode defect.
See this thread at Apple's discussion boards. You basically need to reset you phone. I'm not sure but Ithink there may be a link between seeing this error and using your phone for development but I have no concrete evidence.
I find that if I plug my device in and its set to automatically run iPhoto - then you must let iPhoto load and let it try to sync photos before you quit it. Then you should be able to use XCode to load an application on to your phone.
If you do get the error - unplug the device, turn it off and then back on, and that usually clears up the problem
Related
I'm trying to get ChromeCast working in my swift app using google-cast-sdk. When I found it was not working, I tried the demo app (CastVideos-ios) and got the exact same results (ie. does not connect).
I changed the bundle identifier of the CastVideos-Swift app to my bundle ID so I could run it on my device. I double-checked my App ID in the iOS Dev portal has the WiFi capability enabled, and of course it is enabled in the Xcode project file in both the CastVideos-swift demo, and in my own app.
Additionally, I have verified many times that my iPhone is on the same WiFI network as the ChromeCast device connected to my TV. I have tested the ChromeCast device using the YouTube App - works perfectly. When I tap the ChromeCast button in the YouTube app, it just throws to my "Living Room TV" - doesn't even ask me, I guess because there is only 1 CC device.
When I run the CastVideos-swift demo app (or my app) and I tap the ChromeCast button, I get a popup asking me to choose, and there is ONLY one option "Nearby Device" - from what I read, this seems to indicate that there is already a problem, that the app is treating my CC device like a "Guest" as if it were on a different WiFi, but its not (and again, YouTube app works) - so, I tap Nearby Devices and the Connect fails so I put in the code. Nothing happens in the app or TV, the debugger shows this error:
[GCKCastDeviceController notifyDidFailToConnectToApplicationWithError:], message: Failed to connect to app with error: Error Domain=com.google.cast.GCKError Code=20 "Application was not found" UserInfo={NSLocalizedDescription=Application was not found}
Additionally, it may be important (or not) but I am seeing this message in the logger also, before the failed to connect.
[GCKNNetworkUtils getTwoLowerBytesFromNetworkAddress:], message: Invalid network address
Finally, I find it fascinating that when I connect with YouTube app and cast a video - and then switch to the CastVideos-Swift demo, when I tap the CC button, instead of saying "Nearby devices" it correctly says "Living Room TV" and below that in parenthesis it says "Youtube" - which appears to indicate that it is aware that the YouTube app is currently casting to this device) - and YET, when I tap the Living Room TV device, I get the exact same error (the YouTube streaming continues to play without interruption).
My best idea is that it has something to do with my App ID since i used the same bundle ID for the demo app as my own app. But, except for turning on the WiFi capability, I cant think of anything else which would make it fail that I have read so far.
Note that I read that the YouTube app is not a good test of discoverability (it has access to internal APIs?) - I tried another app which was ChromeCast enabled, and it worked perfectly, no guest mode login, just asked me to pick "Living Room TV" and it worked fine.
Maybe someone here has seen this before? Thanks in advance.
Sadly, it turned out to be a bogus google cast app ID I was given by the project owner.
I ran my iPhone app and its watch extension in the simulator. I send messages from phone to watch and vice versa. The messages are sent and received without any issue. But when I send the iPhone app to background, and then a message is sent from watch to iPhone, I continuously get the following log:
[WC] __33-[WCXPCManager onqueue_reconnect]_block_invoke error reconnecting to daemon due to NSXPCConnectionInterrupted
I searched regarding this but did not find any proper solution. Many have posted it as an issue in the betas of Xcode. I am using the latest Xcode 8.1. What could be the proper solution?
I constructed provider code with using C# and it was able to send notification messages to iphone devices successfully. But since yesterday, it hasn't worked. Also it seems to connect APNS successfully and send notification message. Unfortunately, no notification message is received by iphone device. I controlled internet connection and device token of iphone device. What else can I do? Thanks in advance...
I dont have enough rep to comment on the question so typing out answer - Please add more details and I will edit my answer.
Is this in a developer / testing environment and are you using an ad hoc profile to install the application on the iphone devices?
Did you check if the device token has changed and that you are using the new/ correct token in the C# code?
Do provide more details of your problem.
Crazywood, I don't have a solid answer for you but I can tell you I'm in the same boat as you.
There are times when all my notifications go through and times when none of them seem to.
One guess is that not all notifications are sent. According to the docs, in production remote notifications are not guaranteed to be received by the client. My guess is that this is also the case for the sandbox.
-------- EDIT ------
I went through the trouble shooting list (http://developer.apple.com/library/ios/#technotes/tn2010/tn2265.html) and came across this:
The device may have lost its persistent connection to the push service and can't reconnect. Try quitting the app and relaunching it to see if registration completes the next time. (On iOS 4 and later on devices that support multitasking, you will need to force quit the app from the recents list.) If the registration does not complete, iOS has been unable to re-establish the persistent connection. You can troubleshoot this as described in the previous two sections.
I restarted the app and it made no difference. Then I rebooted my phone. That seemed to do the trick.
I'm trying everything i can to get instruments to profile my app on the actual iphone device, but it won't work no matter what i do. I tried the solution from Does Instruments (ObjectAlloc/Leaks) require the simulator? but that didn't work. Most of the time i get nothing of use from the console, but one time i did receive this error:
Mon Aug 31 11:27:48 unknown
lockdownd[14] : (0x83d400)
handle_connection: Could not receive
USB message #13 from Instruments.
Killing connection
I'm not sure what could be causing this; has anyone else seen this and know a solution?
Same problem - it worked the first two times, then after that never again (even after restarting Xcode, deleiting the device, etc).
Eventually I resorted to:
Set XCode to display the Console
Run with Performance Tool
(instruments starts, and goes "BEEP"
with no error - Apple "forgot" to
include the error message, I think.
ARGH!)
Build&Run on device
Once the (gdb) appears in console,
go to Instruments and select "Attach
to Process" from the drop-down at
top
If you cannot see the name of your
debugging app, wait a second, and
try again
Eventually your app appears in the
list of alread-running stuff, so
select it
Hit the Record button
On subsequent runs, Instruments will remember the name of your app, but will show an error if you hit "record" too soon. So you just keep hitting record and doing "OK" on the process it tries to connect to until it stops messing around and does what it's supposed to.
So far (20 odd runs) this works everytime. Obviously, it would be nicer if it just worked properly, without this manual hackery, but Apple is reporting zero error messages even to system console, so there's nothing we can do!
I have some users testing my app on Windows and Mac platforms. The app crashes at some points but the Windows users cannot get any crash logs. Here's what they do
Run the app and play around till it crashes
Sync their device with iTunes
Look for logs here (on a Vista) C:\Users\\AppData\Roaming\Apple computer\Logs\CrashReporter\MobileDevice\
But there is nothing inside the Apple Computer folder.
Any ideas? Thanks.
Aside from you omitting parts of the path in that it should correctly be containing the login username - ow, now noticed you possibly did try to embed it, hence the double backspace after Users....
Ask your user if he possibly is using multiple computers for syncing his device. In case he does, he should check the machine he used first as those Logs are only synced with the "main"-machine, I believe. Bit of a shot in the dark but worth the attempt, I think.
Ow, and there may be another possible reason I just saw within another thread - credits to Kendall:
If there is not crash log, it could mean the app was shut down for using too much memory - in that case you should see a message come up in the device console indicating your application is being shut down.