Problem testing on iOS devices (SOLVED)

Hi,
I am not sure what I am doing wrong, but I am having issues with testing on iOS device (iPad running iOS 9.3.5). So I am able to install Defold app on the device from the dashboard, but when I tap to start the app it simply does not start. I have tried with tutorial (platformer) project as well as with simple clean project. Is this a common issue or I am doing something wrong?
Thanks

Hmm, strange. I’m guessing you followed these steps? It should work as far as I know.

Does the app say anything in the log? (Check in XCode -> Window -> Devices to see the console log)

Thanks for the quick reply. Nothing in the Xcode log - under devices I see Defold icon under Installed Apps, version 1.0 and identifier is dmengine. When I tap the app icon, black screen appears for a sec and that’s it. Log file clean.

Just to verify my development and distribution iOS provisioning profiles, I have created simple SpriteKit app in Xcode and signed it with those and it works just fine. So profiles are fine.

I have couple of other iOS devices and will try on those.

UPDATE: Same on iPhone 6 Plus with iOS 9.3.5.

Ok, I’ll try to test this tomorrow at work

Ok, I just tried it on an iPhone 6+ running iOS 9.3.2, and it works for me. Unfortunately, I’m not sure what to test next.
Maybe you could try to bundle the game, and deploy it via xcode or ios-deploy. (Not sure why that would work better though since you’d still sign it with the same profiles)

Could you check on your device; Settings -> General -> Profiles & Device Management, select the profile you signed with and make sure it is trusted.

Thanks for the feedback. Couple of points:

  1. Provisioning profiles are not visible in Settings UI anymore - so I have installed Apple Configurator 2 app.
  2. Apple Configurator app has console which shows output from the connected device.
  3. When I tap on Defold dev app the following is presented in the console:

Sep 14 13:01:24 iPad-Mini SpringBoard(FrontBoard)[54] : Unable to obtain a process handle for FBApplicationProcess: 0x1705f7100; dmengine; pid: 429
Sep 14 13:01:24 iPad-Mini mediaserverd(CoreMedia)[24] : -CMSessionMgr- CMSession: Client dmengine with pid ā€˜429’ is now Terminated. Background entitlement: NO
Sep 14 13:01:24 iPad-Mini sharingd[201] : SystemUI unknown identifier: 'dmengine’
Sep 14 13:01:24 iPad-Mini symptomsd(SymptomEvaluator)[124] : 429 dmengine: Terminated (most elevated: Terminated)
Sep 14 13:01:24 iPad-Mini symptomsd(SymptomEvaluator)[124] : Entry, display name dmengine uuid (null) pid 429 isFront 0
Sep 14 13:01:24 iPad-Mini symptomsd(SymptomEvaluator)[124] : Duplicate removal of display name dmengine

  1. I have checked all the provisioning profiles and everything looks good there (also all profiles are now visible from Apple Configurator app).

My next step will be to clean up all profiles and start with the clean slate. Will provide update, but if you can conclude something from the above console output please let me know.

Thanks again for all the help.

2 Likes

Ok so I have removed all signing certs and profiles from my developer account, created new certs and profiles and now it works fine. Thanks guys for help. Next time I hope will have more interesting topic for the forum. :slight_smile:

5 Likes

Do you have plans to make possible to make cloud build of dmengine with user own extension for testing?

If you choose ā€œSign and Uploadā€ from Editor 1, it should upload the dmengine to the dashboard, so that your team mates can test it.

yes, but I told about my custom dmengine with my own native extensions. Or it is already building dmengine with custom native extensions?

Yes, if you have a native extension on iOS, it builds on the cloud server.
And if you choose ā€œSign and Uploadā€, it uploads the custom engine.

5 Likes

WOW! Just WOW!

6 Likes

and what about android dmengine ? Where I can get dmengine build with my native extensions?

1 Like

Currently, the dmengine ends up in <project folder>/build/armv7-android/libdmengine.so (with classes.dex)

It’s a good point that we might want to have an apk available as well at some point.

4 Likes