-
Notifications
You must be signed in to change notification settings - Fork 23
Error 404 deploying to ios device after xcode upgraded to 8.3.2 #31
Comments
I also get this issue. I can run a debug build to 'Local Device' but with 'Remote Device' I get 404
If i call the deploy address in chrome back on windows machine I get
for reference if i extract the .ipa i don't have a SC_Info folder, the only .plist is 'Payload/SpeMobile UAT.app/Info.plist' |
@domisginger thanks for that. I thought I was alone on this one :-) |
@BigFoppa I've also got the same issue. I'll be looking more in dept today. |
The deploy 404 starts when I run "brew upgrade libimobiledevice --HEAD" in accordance with this: The short answer seems to be that when not using the --HEAD for libimobiledevice remotebuild is able to run /deploy and return HTTP 200. When using --HEAD for libimobiledevice, remotebuild returns 404 on deploy. The strange thing about this is that the app actually deploys when remotebuild returns 404, but doesn't deploy when it returns 200. This is deployment to physical devices. I get some warnings;
That's how far I've gotten. |
I tried running |
@BigFoppa Have a look at this, it's the same problem I'm having. I tried deployment using ideviceinstall and it gives a seg fault 11 as described: libimobiledevice/ideviceinstaller#70 |
@jlyshoel Yes, I agree, that seems to be the same problem. Thanks for the hint. |
@AnBucyk this may not be your problem. But if it is please have a look at the issue reported here: : libimobiledevice/ideviceinstaller#70 |
Closing this as a dupe of #26. If this issue persists after 26 is fixed, feel free to reopen. |
@drewgillies I was in issue #26 explicitly asked to create a new issue for this problem. As I see it it should stay open and is not a duplicate of #26. |
@drewgillies I can not see that I can reopen this issue. |
I've also got the same issue... PC: VisualStudio2015, node4.8.3, npm2.15.11, cordova6.5.0 Could you give me some advice? |
@Ashley9 I am building and deploying to Local device instead of remote. Had problems locating the DeviceSupport folder on the Mac, the path in the documentation did not exist. Searched the mac for DeviceSupport and copied the files to the pc. That worked. But debugging don't. |
I'm having the same issue.... |
Hi, build successful but failing to deploy to IOS device. it is bringing up itunes and then shows the app there and device is identified but says error occured continue or not? and fails. one error result states, version mismatch other says device may not be connected and awake. I am using ipod 9.3 version ios and another one iphone 5s with 10.2.1 ios. I am building apache cordova app in visual studio 2017 with macincloud remotebuild. how to resolve this!? any hint is a big help!! I am manually deploying but can't debug. if i deploy, i am getting network error at xmlhttprequest and but same code working fine in simulator. when press button then and i restart app then it is dumping a big error message and showing exitapp though i am not using any of that plugin or code line. how to debug on device is first priority which may help to resolve rest. 1>Time Elapsed 00:05:02.04 |
@BigFoppa I'm sorry for the late reply. |
Does remotebuild support XCode 8.3.2 ? To compile and publish an app ? |
@fedlerner remotebuild Supports Xcode 8.3.2 but to publish an app , you need to copy the |
Hi guys, do you still have the same issue? |
Hello, issue is still present. (I'm using VS 2015 community edition) |
hello. same problem here. is there no solution at all? |
I changed to an ipad, and it works 👍 |
@Webrusterkk is there a tutorial online on how to proceed ? |
@fedlerner unfortunately there are not any usefull online tutorial at one place, for start up i would recommend to start from the VS Docs |
As I have described in my comments to issue #26 I can not deploy to Remote device from Visual Studio 2015. I am able to build after the latest changes to remotebuild but not deploy.
My current setup:
PC: VS2015, Cordova 6.4.0, ios 4.3.1
Mac: macOS 10.12.4, xcode 8.3.2 and cordova 6.4.0 globally installed.
This is the message after debug build to Remote device:
I believe I have tried everything that is suggested around this kind of issue.
The text was updated successfully, but these errors were encountered: