I tried to sign my iOS app but after have created the app ID and generated the iOS certificate and the provisioning profile, when I try to sign my app with those data I receive the error described here
Hi! It looks like you're not logged in to the defold server, and we apparently don't check that before attempting to sign. As a workaround while we solve the actual problem, you could try to provoke a login by synchronizing your project or restarting and clicking import project.
After investigating further it appears you are indeed logged in, but somehow are not authorized to upload a signed ipa to the dashboard. I'm having trouble figuring out how this could happen. Could you locate an editor2.*.log file for a session that exhibits this problem under ~/Library/Application Support/Defold and send it to me on the Defold forums? I'm mats.gisselson. If you could send me a direct message with a log file it would help a lot!
Thanks for the log! It looks like your project uses Native Extensions? We found several issues that prevented iOS app signing from working in projects using Native Extensions. A fix is coming for these.
Yes, I'm working in a personal project with Native Extension to participate to the Kingfomarket contest.
I hope you could have a fix soon.
Thank you very much.
We've just merged a fix that should hopefully solve your problem. You should see an update to the editor within an hour or so. Please let us know if you have any more issues!
After updating the editor and trying to bundle the iOS Application, I still have the same error...
com.dynamo.bob.MultipleCompileExceptionError: Build error
com.defold.extender.client.ExtenderClientException: Failed to build source.
Yes, using this we were able to track down the error report from the Native Extension build servers. It seems your extension uses the new Speech framework from iOS 10.0. Sadly, our build servers are still on the iOS 9.0 SDK. We have it on our roadmap to update to 10.0, but some work still remains before that can happen.
But all is not lost! I'm told that you can bundle frameworks with your project. Simply create a lib folder below your extension and an ios folder below the lib folder. Then copy the Speech.framework from the iOS 10.0 SDK into your extension/lib/ios folder. You can then remove "Speech" from the frameworks listed in the ext.manifest file. After that the build servers will use Speech.framework from the extension/lib/ios folder, and you should hopefully be able to build your project.
In the meantime I'll try to ensure we extract as much information as possible from the errors we get from the servers. The error message should have mentioned the Speech framework to give you some hint about what could have gone wrong. Since Native Extensions is kind of new, we're still working out the kinks. Sorry about that.
I'm sorry but, even after creating the folder that you suggested and putting there the Speech.framework, I still have the same problem generating the bundle.
This is the error that I have:
Sadly, there is not much information to be gained from that error report. I've reached out to you on internal channels to ask if you're comfortable sharing your project with us so we can help shepherd it through the build process. In the process we hope to learn about the various pitfalls that can occur and ensure we show helpful build errors.
Expected behaviour
Actual behaviour
Steps to reproduce
I tried to sign my iOS app but after have created the app ID and generated the iOS certificate and the provisioning profile, when I try to sign my app with those data I receive the error described here
Hi! It looks like you're not logged in to the defold server, and we apparently don't check that before attempting to sign. As a workaround while we solve the actual problem, you could try to provoke a login by synchronizing your project or restarting and clicking import project.
After investigating further it appears you are indeed logged in, but somehow are not authorized to upload a signed ipa to the dashboard. I'm having trouble figuring out how this could happen. Could you locate an
editor2.*.logfile for a session that exhibits this problem under~/Library/Application Support/Defoldand send it to me on the Defold forums? I'mmats.gisselson. If you could send me a direct message with a log file it would help a lot!Thanks for the log! It looks like your project uses Native Extensions? We found several issues that prevented iOS app signing from working in projects using Native Extensions. A fix is coming for these.
Yes, I'm working in a personal project with Native Extension to participate to the Kingfomarket contest. I hope you could have a fix soon. Thank you very much.
We've just merged a fix that should hopefully solve your problem. You should see an update to the editor within an hour or so. Please let us know if you have any more issues!
After updating the editor and trying to bundle the iOS Application, I still have the same error... com.dynamo.bob.MultipleCompileExceptionError: Build error com.defold.extender.client.ExtenderClientException: Failed to build source.
Maybe this could help...
Expected behaviour
Actual behaviour
Steps to reproduce
Yes, using this we were able to track down the error report from the Native Extension build servers. It seems your extension uses the new Speech framework from iOS 10.0. Sadly, our build servers are still on the iOS 9.0 SDK. We have it on our roadmap to update to 10.0, but some work still remains before that can happen.
But all is not lost! I'm told that you can bundle frameworks with your project. Simply create a
libfolder below your extension and aniosfolder below thelibfolder. Then copy theSpeech.frameworkfrom the iOS 10.0 SDK into yourextension/lib/iosfolder. You can then remove"Speech"from the frameworks listed in theext.manifestfile. After that the build servers will useSpeech.frameworkfrom theextension/lib/iosfolder, and you should hopefully be able to build your project.In the meantime I'll try to ensure we extract as much information as possible from the errors we get from the servers. The error message should have mentioned the Speech framework to give you some hint about what could have gone wrong. Since Native Extensions is kind of new, we're still working out the kinks. Sorry about that.
I'm sorry but, even after creating the folder that you suggested and putting there the Speech.framework, I still have the same problem generating the bundle. This is the error that I have:
Expected behaviour
Actual behaviour
Steps to reproduce
Sadly, there is not much information to be gained from that error report. I've reached out to you on internal channels to ask if you're comfortable sharing your project with us so we can help shepherd it through the build process. In the process we hope to learn about the various pitfalls that can occur and ensure we show helpful build errors.
You should now have much better error reporting from Native Extension builds. Please let us know if you have further issues!