-
Notifications
You must be signed in to change notification settings - Fork 466
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ERROR: Assertion Failed #11
Comments
I'm hitting the same assert with ios-deploy 1.0.4. |
Try 1.0.5/1.0.6 |
@shazron Still experiencing the mentioned issue with |
I am experiencing the same issue with the same configuration as @rvanbaalen. |
It doesn't happen every time for me, but seemingly at random. |
I am experiencing same issue running node 10.0.28, cordova 3.5.0, iOS 7.1, mac osx 10.9. ** BUILD SUCCEEDED ** [....] Waiting for iOS device to be connected |
same here, using ios-deploy@1.0.8 UPDATE: Started working again after downgrading to cordova@3.4.1-0.1.0 (well, I actually uninstalled cordova and ionic first, and have done several other things so cannot be 100% sure that's related with cordova version but I suppose so) |
Same happened to me earlier. Traced it through the ios-deploy code and found it was failing on Pairing Assertion. The device was connected but not paired correctly. Disconnected the device and reconnected it -- the assertion succeeded and the deployment went through correctly. |
It happens to me as well:
In the mean time, is it possible to debug through Xcode? |
I'm hitting it as well...
Any update on the issue? |
Hi, Any update on this issue? I've the latest phonegap-cli and it was working fine last week. I don't think it's the issue here but this problem started happening after I added the "local" to "phonegap local build ios". I tried to update the phonegap-cli and dependencies and even did a restart. Sometimes it runs well then it stops working. I believe that if you disconnect the device and plug it in as you're starting the build forces some sort of pairing that makes it work if the timing is correct. But until this week I never had to reconnect the device and now it's the only way to make it work (although still 60% chance). edit |
Bump.
** Edit ** Ok, so for me I just needed to unplug and replug the iOS device and it worked. What confuses me is that the script says ”Found device” with the device ID. |
Ok, I'm super stressed out about this bug, so stressed out I checked out ios-deploy's source code and started to debug it. While I haven't found a reason or (software) fix for it yet, I've made an important discovery I wish to validate with other people with the same issue. Anyone with the issue please test one step at a time:
Also note that the effect isn't immediate, in my case I hadn't Wifi Sync on to begin with, but each time after I turned Wifi off it would fail on attempts within 30-60 seconds but then work flawlessly. So turn wifi off, wait 30s then test the deploy again. I know this isn't a good permanent solution but it might indicate the source of the problem. I'll post any new findings I make, if there are some! edit edit 2 |
Just did a pull request to help diagnose this problem. First, some new information. In my case I found out that while I had an iPhone on an USB docks, after a while my iPad would ping the mac and get detected by ios-deploy. Until I realized the device uuids were different I thought OSX was "upgrading" the connection although the iPhone's Wifi was off. Thing is, I've both devices with Wifi Sync disabled on iTunes so I'm still not sure why this is happening. My pull request helps this issue by improving the current log message that only shows the device's ID. It now shows the name, model, id and tells how it's connected (USB or WIFI). In my current tests I've changed the code to make it work over WIFI and everything works (the deploy) but the debugger won't launch. This code is not included in this pull request, so if your device is shown as connecting through WIFI it shouldn't even deploy correctly and will not show the device's name but tells you it's a WIFI connection. |
I've done all I could for this issue and it's no longer a problem for me. The pull request #48 should help everyone diagnose their problem and adds a couple nice features like Wifi deployment. Perhaps most importantly, it removes the puzzling "assert" log. Right now, it's working for me, if anyone can test (specially with devices other than the iPad Mini and iPhone 5S) it would be nice to know if everything still works. |
PR #48 merged in and lightly tested. The changes are in master, so if any of you want to test it out. Thanks @alexmipego! Please report if it fixes your problem, and the issue can be closed. |
I'm having the same issue, I'm using cordova version 3.5.0-0.2.4 on a mac with OSX 10.9.4, what else could I do? Last week I was able to run my application on my iphone with iOS 7.1.2, the only thing I changed was adding a google analytics plugin but I already removed it and still not working. Another thing is that every time I add a plugin I get some weird errors and I have to remove the ios platform and add it again. |
I'm not sure about the structure and "link" between projects. Try updating ios-deploy which should be a cordova dependency. Checking the source code of package.json it should update to version 1.1.0 which appears to include the patch this issue mentions. "npm -g outdated ios-deploy" should tell you if an update is available. |
That solved the issue for me ... thanks a lot! (Now if anyone would care to fix PG build someday ... ;) |
What do you mean by PG build? (link...?) |
I'm seeing the below "Assertion failed" and "Abort trap" errors; ios-deploy is used via Ionic Framework's LiveReload feature. I'm on iOS 7, Xcode V5.1, Cordova V3.5.0-0.2.7, ios-deploy V1.1.0, and Ionic CLI V1.2.4.
|
update and try version 1.2.0 |
I have the same issue. Error message: Reproduced only on iOS 6.x, on iOS7.x and iOS8.x is all ok. |
Thanks stigor - we may have come up to the limitation that the interfaces that came with Xcode 6 may not support iOS 6. The IDE itself does not even come with support for any iOS 6 simulators, for example. Just a hunch. |
I'm getting: [ 0%] Looking up developer disk image XCode 6.1 |
After an update to 1.3.0 i constantly get |
Not enough information for repro. Kill all lldb processes? Crash log? |
Sorry about that. Date/Time: 2014-11-14 21:49:55.888 -0500 Sleep/Wake UUID: Time Awake Since Boot: 23000 seconds Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) VM Regions Near 0: Thread 0 Crashed:: Dispatch queue: com.apple.main-thread Thread 1:: Dispatch queue: com.apple.libdispatch-manager Thread 2: Thread 3: Thread 4: Thread 5: Thread 6: Thread 7:: com.apple.CFSocket.private Thread 0 crashed with X86 Thread State (64-bit): Logical CPU: 1 Binary Images: External Modification Summary: VM Region Summary: REGION TYPE VIRTUAL Model: MacBookPro6,1, BootROM MBP61.0057.B0F, 2 processors, Intel Core i7, 2.66 GHz, 8 GB, SMC 1.57f18 |
Killall lldb did not help.
|
Also this was red in terminal
|
I'm seeing the same issue as @softBarbarian, and I'm pretty sure it's related to #80 – the exit code from With iPhone 4S attached: $ ios-deploy -c --timeout 2
[....] Waiting up to 2 seconds for iOS device to be connected
[....] Found iPhone 4S 'iPhone 4S' (4bc5ee6577df39826d45e0d871bc538b28eb9d84) connected through USB.
[....] No more devices found.
$ echo $?
253 With no device attached: $ ios-deploy -c --timeout 2
[....] Waiting up to 2 seconds for iOS device to be connected
[....] No more devices found.
$ echo $?
253 For completeness, the version of $ ios-deploy --version
1.3.1 |
Ugh I see the flaw in my patch :/ will fix soon |
Hi ShazronIs 1.3.1 turning on the -d implicitly and returning zero if at least one device was found for -c |
Thanks @senthilmanick that helped, --debug needs to be turned on implicitly. I've fixed the underlying problem in #80 |
#80 has been re-fixed, and 1.3.2 was published. |
@shazron I found I was getting this error when the path to the application was incorrect [ Running the following command manually with the .app file path allowed me push without issues to a device.
So I think I could replicate an assertion error and throw "ios-deploy quit unexpectedly" as follows:
|
I had the same issue. My fix was to allow my iOS device to "trust" my computer. It was easily overlooked when re-installing OS X. |
I have the same issue with OSX Yosemite and ios-deploy v1.4.0. Killing old instances of lldb didn't help.
|
1.5.0 has some improvements, let me know. https://github.com/phonegap/ios-deploy/releases/tag/1.5.0 |
I had been getting the same as @drastick:
I realized that I had a beta of Xcode selected through Next, I got this:
Strangely enough, I don't even have WiFi Sync enabled, according to iTunes. And yes, the device is plugged in through a simple lightning USB cable. The app was getting on the phone, but it wasn't getting run. So, next I deleted the app and tried again. Now, I get this:
Again, the app gets successfully deployed to the phone, but it doesn't get run. My config:
Apologies if this is actually a cordova or ionic issue, but I'm thinking it's ios-deploy. |
@listrophy you mentioned that it is installed but doesn't run. Can it run manually? (just checking the integrity of the install) |
@listrophy, in the root of your cordova app, can you run:
Substitute YOURAPPNAME for your app's name. If you get an error, paste it here. |
I think that I've finally found the cause of my issue. I'm using a german umlaut (
|
@ohh2ahh thanks, I'll file a new issue. Just to confirm, if you just use ascii letters in your app name it works fine, yes? (trying to rule out other issues) |
Filed #147 |
@shazron Yes, without the umlaut everything works perfectly fine. Re-adding the umlaut brings the same issue back. Thanks for your effort, I appreciate it very much! |
@listrophy I have the same issue with iOS 8.4 and Xcode 8.4. Just shutting down your phone and restart again will fix the problem in my case. See #155. |
Fixed in #56 |
I get the following error whenever I try to deploy anything to a device:
Assertion failed: (AMDeviceStartService(device, CFSTR("com.apple.debugserver"), &gdbfd, NULL) == 0), function start_remote_debug_server, file ios-deploy.c, line 524.
/Developer/Projects/Pathem/App/Platforms/ios/cordova/run: line 125: 15533 Abort trap: 6 ios-deploy -d -b "$DEVICE_APP_PATH"
I'm using the most recent version of ios-deploy and cordova (3.1.0).
The text was updated successfully, but these errors were encountered: