Hello Everybody!
Today OS X 10.11 will be released and I’m sure that everyone will want to upgrade. However, we have discovered an issue with the Tizen SDK that prevents deploying apps to your Tizen devices.
At this time we recommend that you DO NOT upgrade to OS X 10.11 if you are developing Unity applications for Tizen.
We will keep you updated if any workarounds or solutions are discovered.
Thanks!
David Rogers
It’s has an error after deploy on emulator too, it can’t be launch app.
Test on:
OS X 10.11
Unity3d 5.2.1p4
Tizen SDK 2.3.1 → Emulator has CPU VT error “No accelerator found”
and
OS X 10.10
Unity3d 5.2.1f1
Tizen SDK 2.3.0_Rev3
error log like below:
D/LAUNCH ( 2476): launchpad.c: __real_launch(229) > [SECURE_LOG] [/opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird:Platform:launchpad:done]
E/AUL_PAD ( 2476): preload.h: __preload_exec(124) > dlopen(“/opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird”) failed
E/AUL_PAD ( 2476): preload.h: __preload_exec(126) > dlopen error: /opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird: cannot open shared object file: No such file or directory
D/AUL_PAD ( 2476): launchpad.c: __normal_fork_exec(190) > start real fork and exec
D/AUL_PAD ( 2160): launchpad.c: __send_result_to_caller(555) > – now wait to change cmdline –
E/AUL_PAD ( 2476): launchpad.c: __normal_fork_exec(204) > unknown executable error - /opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird
D/AUL_PAD ( 2160): launchpad.c: __send_result_to_caller(555) > – now wait to change cmdline –
I/AUL_PAD ( 2160): sigchild.h: __launchpad_sig_child(142) > dead_pid = 2476 pgid = 2476
I/AUL_PAD ( 2160): sigchild.h: __sigchild_action(123) > dead_pid(2476)
D/AUL_PAD ( 2160): sigchild.h: __send_app_dead_signal(81) > send dead signal done
I/AUL_PAD ( 2160): sigchild.h: __sigchild_action(129) > __send_app_dead_signal(0)
I/AUL_PAD ( 2160): sigchild.h: __launchpad_sig_child(150) > after __sigchild_action
E/AUL_PAD ( 2160): launchpad.c: __send_result_to_caller(544) > error founded when being launched with 2476
see full error log in attach file.
2343974–158583–error.txt (326 KB)
GameDevToDied:
It’s has an error after deploy on emulator too, it can’t be launch app.
Test on:
OS X 10.11
Unity3d 5.2.1p4
Tizen SDK 2.3.1 → Emulator has CPU VT error “No accelerator found”
and
OS X 10.10
Unity3d 5.2.1f1
Tizen SDK 2.3.0_Rev3
error log like below:
D/LAUNCH ( 2476): launchpad.c: __real_launch(229) > [SECURE_LOG] [/opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird:platform:launchpad:done]
E/AUL_PAD ( 2476): preload.h: __preload_exec(124) > dlopen(“/opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird”) failed
E/AUL_PAD ( 2476): preload.h: __preload_exec(126) > dlopen error: /opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird: cannot open shared object file: No such file or directory
D/AUL_PAD ( 2476): launchpad.c: __normal_fork_exec(190) > start real fork and exec
D/AUL_PAD ( 2160): launchpad.c: __send_result_to_caller(555) > – now wait to change cmdline –
E/AUL_PAD ( 2476): launchpad.c: __normal_fork_exec(204) > unknown executable error - /opt/usr/apps/com.studiomoji.hungrybird/bin/hungrybird
D/AUL_PAD ( 2160): launchpad.c: __send_result_to_caller(555) > – now wait to change cmdline –
I/AUL_PAD ( 2160): sigchild.h: __launchpad_sig_child(142) > dead_pid = 2476 pgid = 2476
I/AUL_PAD ( 2160): sigchild.h: __sigchild_action(123) > dead_pid(2476)
D/AUL_PAD ( 2160): sigchild.h: __send_app_dead_signal(81) > send dead signal done
I/AUL_PAD ( 2160): sigchild.h: __sigchild_action(129) > __send_app_dead_signal(0)
I/AUL_PAD ( 2160): sigchild.h: __launchpad_sig_child(150) > after __sigchild_action
E/AUL_PAD ( 2160): launchpad.c: __send_result_to_caller(544) > error founded when being launched with 2476
see full error log in attach file.
Sorry, we don’t officially support the Tizen emulator.
The best place to seek help regarding Tizen SDK (not Unity related) issues is in the Tizen forums. https://developer.tizen.org/forums
S_P
October 22, 2015, 9:27am
4
Is it solved with OSX 10.11 in unity 5.2.2?
It’s actually not a Unity issue. Samsung has given a workaround that works great. Go here http://www.samsung.com/us/smart-switch/ and install Samsung SmartSwitch. Just install and that’s it!