@mh I did further tests and I can see that for this Android Application here:
The app hangs on a brand new install of the Xamarin Android Player / Nexus 7 (marshmallow)
This is what happens on a real device too (Nexus 7 as well);
Both devices are attached to the adb:
macbookproloreto:~ admin$ adb devices
List of devices attached
10.71.34.101:5555 device
0a21584f device
and I can run from Fire so I see from the CrossBox devices popup then.
I confirm that the configuration of devices / adb / android seems to be ok, since
- Using Fire on a real Nexus 7 device I the same “Waiting for Debugger” popup and then the error;
- Using
AndroidStudioI can run the project without this debugging error. The AndroidStudio project can be found here: https://github.com/loretoparisi/swift-promise-example/tree/master/SampleAndroidApp
This is the emulator logs (That hangs running from Fire):
03-03 16:22:27.856 1491 1491 D AndroidRuntime: Shutting down VM
03-03 16:22:27.863 330 957 I ActivityManager: Start proc 1501:org.me.androidsilversampleapp/u0a52 for activity org.me.androidsilversampleapp/.MainActivity
03-03 16:22:27.871 1491 1494 I art : Debugger is no longer active
03-03 16:22:27.889 1501 1501 W ActivityThread: Application org.me.androidsilversampleapp is waiting for the debugger on port 8100...
03-03 16:22:27.890 1501 1501 I System.out: Sending WAIT chunk
03-03 16:22:27.926 330 1296 I OpenGLRenderer: Initialized EGL, version 1.4
03-03 16:22:27.949 805 955 E Surface : getSlotFromBufferLocked: unknown buffer: 0xaf0f2380
03-03 16:22:27.956 330 1296 W EGL_xap : eglSurfaceAttrib not implemented
03-03 16:22:27.956 330 1296 W OpenGLRenderer: Failed to set EGL_SWAP_BEHAVIOR on surface 0x9db933e0, error=EGL_SUCCESS
03-03 16:22:28.093 1501 1507 I art : Ignoring second debugger -- accepting and dropping
03-03 16:22:31.456 330 563 D TaskPersister: removeObsoleteFile: deleting file=16_task.xml
03-03 16:22:31.456 330 563 D TaskPersister: removeObsoleteFile: deleting file=16_task_thumbnail.png
03-03 16:22:37.851 330 394 W ActivityManager: Launch timeout has expired, giving up wake lock!
03-03 16:22:41.665 330 534 E WifiStateMachine: WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=any RSSI=-55
03-03 16:23:01.667 330 534 E WifiStateMachine: WifiStateMachine CMD_START_SCAN source -2 txSuccessRate=0.00 rxSuccessRate=0.00 targetRoamBSSID=any RSSI=-55
I don’t get what means this message from Art:
03-03 16:22:27.871 1491 1494 I art : Debugger is no longer active
that makes a lot of sense as soon as we look at the popup on the device emulator.
So the issue was that running as a Release configuration it start debugging, while running as Debug configuration, debugging starts since I can see:
03-03 16:26:13.967 1593 1599 I art : Debugger is active
03-03 16:26:13.983 1593 1593 I System.out: Debugger has connected
03-03 16:26:16.193 1593 1593 I System.out: waiting for debugger to settle...
03-03 16:26:16.282 330 563 D TaskPersister: removeObsoleteFile: deleting file=19_task.xml
03-03 16:26:16.282 330 563 D TaskPersister: removeObsoleteFile: deleting file=19_task_thumbnail.png
03-03 16:26:16.394 1593 1593 I System.out: debugger has settled (1425)
To recap, the Release configuration seems to start a debugging session, that is the error (not sure it’s my side or Android Application template side…