I keep on getting the message attached when I try to build and copy to device. It builds it, just doesn’t copy it.
When you connect the device, the device pops up a dialog about ‘trusting this computer’. Did you click yes?
Also, debug certificate or production?
You want to double check all your certificates.
You might also want to show us a screenshot of the Corona ‘build setup’ dialog.
I did hit trust.
I have tried an Ad Hoc Distribution Provisioning Profile and a Deveopment Provisioning Profile. I think my certifictes are fine.
The app builds correctly. It just doesn’t copy to the device. It even runs in the simulator. Check the logs in the attachments.
The main problem that comes up looks like: Error finding pathto/ios_sendapp.sh
However, it is there.
… You might also want to show us a screenshot of the Corona ‘build setup’ dialog.
Can you start Xcode and make sure you have any extras installed and then if so, in Xcode go to Window->Devices & Simulators and make sure your device shows up, goes through all of the development setup etc.
Rob
I am busy now, but I will get back to you guys the 26th.
The device was setup. I couldn’t attach the screenshots, so check the ones out on the pdf at https://drive.google.com/file/d/0Bw_oMQkFFuU-djBhTUF0bHM3RFF2WG11YmVvb3d3MEJvSVRj/view?usp=sharing
When posting, you can click ‘more reply options’ below to get a menu for attaching images and files.
That all looks good.
How about the result of the advice from Rob. I’m particularly keen to know if xCode is seeing your device as attached.
It is seeing the device as attached and configured
Sorry, I should have asked these things earlier:
-
What version of Corona are you using?
-
What Version of OS X are you running?
-
Are you able to build it with the ‘do nothing’ option, then installed it to your device using the xCode devices view?
I wonder if you’re blocked entirely or if this is just a weird Corona problem. My guess is this will also be blocked.
- Was that wild-card certificate made for your device?
I know it’s a silly question, but I have to ask, because if that device is not in the certificate list it won’t be able to install on the device.
I may think of more questions later.
- Is the app already installed on your device? If so, delete it like you would any other app, then try again.
It may not like having the app on the device if you’ve changed certificates for the current build.
- Have you enabled the device for development? This is something you used to have to do (I’m not sure if this is required any more) and you did it via xCode. Until then, you could not install apps from xCode.
https://apple.stackexchange.com/questions/159196/enable-developer-inside-the-settings-app-on-ios
- Have you resolved the warning about the launch assets and settings? This probably won’t block installing on your own device, but you’ll need to resolve it to do a real release, so best to get that right just in case.
-
3188
-
10.12.6
-
Blocked
-
Made for the Device
-
No
-
It is Setup for Development in the default, new way
-
No
Thanks!
Now, it says "ERROR: code signing failed: /Users/Strong621/Desktop/Luke’s Apps/GK/Gram K.app: replacing existing signature
/Users/Strong621/Desktop/Luke’s Apps/GK/Gram K.app: unknown error -1=ffffffffffffffff"
Okay, I just ran some tests. It is an unknown signing issue. Should I post my code on Github?
I doubt posting code is going to help with signing issues. Is that error coming from a Corona dialog? Is it in our Console log? Is it in the Xcode device console log?
What happens if you try to use Xcode’s Devices & Simulators to install the app instead of Corona?
Rob
The error is coming from Corona. It comes up in the logs, and it alerts me. There is an error when I try to run it only on a real phone, it works fine in the simulator. Lastly, it says unknown error when I try to install it to the device through the devices/simulators tab.
Can you copy/paste the exact message from the console log?
Rob
I attached a screenshot.