Unable to start Device Manager on mac OS Sonoma 14.0

I think you should. This is unacceptable.

2 Likes

I am experiencing the same issue and it’s a real blocker to develop anything to run on Tizen devices. At the very least we need some workaround until the full support is provided. The timescales suggested by Tizen team are shocking. We have already put the Tizen development on hold in the recent months exactly because of the Tizen Studio incompability with the latest iOS system but I expected that by now this issues would have already been sorted.

2 Likes

MacOS Sonoma
Due to issues in the recent version of macOS Sonoma it will not be supported in the Tizen Studio until a planned release in spring of 2024.

There is a work around for those who are facing issue in launching Device Manager in macOS Sonoma, they can use following CLI commands for similar functionality.

  1. permit for install -

$ /tools/sdb devices
List of devices attached
emulator-26111 device t-1019-1

$ /tools/ide/bin/tizen install-permit -s emulator-26111
Install Permitted

  1. Install the app -

$ /tools/ide/bin/tizen install -s serial -n pkgname – <path to base dir of tpk/wgt>
e.g - $ /tools/ide/bin/tizen install -n org.tizen.basic-1.0.0-i386.tpk -s emulator-26101 – ~/workspace/basic/Debug

1 Like

Hi there!
I faced the same problem after MacOS update.
Another thing that you guys can do is try to open remote device manager. It allows to add and connect to remote devices(tested on TV devices only)

This is utterly unacceptable. Should developers just sit and wait until March 2024? Or should we go ahead and rollback our own computers operating systems to accomodate the fact that Samsung and the Tizen Studio team simply do not care about devs?

I can’t speak for the Tizen Studio development team but I thought macOS Sonoma is still considered Beta until March. At least that is how MacWorld described the last update a few weeks ago.

But if it makes you feel any better the Windows 10 computers updated to Windows 11 also have this same problem and there is no plan to fix that.

Ron
Samsung Developer Relations

I am also on Sonoma and am finding that major critical portions of tizen studio don’t work. Device Manager and Emulator Manager are the most important ones I’ve found so far. This is effectively making it impossible to develop any applications.

Hi! I’m new to this and I get the following issue attempting to run those commands

josh@Joshs-MacBook-Air ~ % /tools/sdb devices
zsh: no such file or directory: /tools/sdb

Sonoma beta 1 was released back in June 2023. And the Stable/Official version was release in September, so the above makes no sense.

The fact that Windows is also affected is terrible. It’s going to be challenging to explain to customers why their products based on Samsung hardware can’t be updated due to this.

@joshatticus
Sonoma beta 1 was released back in June 2023. And the Stable/Official version was release in September, so the above makes no sense.

I accept that as a fact, and apologize. I haven’t used Mac in 20 years I was just going by what MacWorld called it.

Windows 10 → 11 was a Microsoft update issue in removing some necessary .DLLs but there was a simple fix.

Ron
Samsung Developer Relations

@r.liechty_SDR I tried the workaround of using tizen install-permit for my TV device (not the emulator) and am getting a message saying “Please check the active certificate profile”. I can’t find any documentation around the install-permit command, and I am not providing a package with the command, so I’m confused as to how the certificate profile relates to this step. Can you provide some assistance?

Hi! @r.liechty_SDR have you any updates? Tizen development now blocked and it’s terrible.

This is the best information I have.

Due to issues in the recent version of macOS Sonoma it will not be supported in the Tizen Studio until a planned release in spring of 2024.

There is a work around for those who are facing issue in launching Device Manager in macOS Sonoma, they can use following CLI commands for similar functionality.

  1. permit for install -

$ /tools/sdb devices
List of devices attached
emulator-26111 device t-1019-1

$ /tools/ide/bin/tizen install-permit -s emulator-26111
Install Permitted

  1. Install the app -

$ /tools/ide/bin/tizen install -s serial -n pkgname – <path to base dir of tpk/wgt>
e.g - $ /tools/ide/bin/tizen install -n org.tizen.basic-1.0.0-i386.tpk -s emulator-26101 – ~/workspace/basic/Debug

Note I have not tried this as I don’t have a Mac

Ron
Samsung Developer Relations

Make Sure The Certificate profile has a Samsung (Tizen) Distributor certificate and not a Tizen Certificate. If you have both that will mess it up too. Samsung only works with the Samsung Certificate.

Ron
Samsung Developer Relations

I am having the same issue. The icon in the dock shows up for a second and then changes to a folder icon and disappears.
In the logs I see this:

[2024.3.9 2:25:48.478][INFO][Main.initializeLogger] Start Device Manager!!
[2024.3.9 2:25:48.494][INFO][Main.obtainLockFile] The First Device Manager Running
[2024.3.9 2:25:50.981][WARNING][Main.main] Throw exception: Exception in Application start method
[2024.3.9 2:25:50.982][WARNING][DeviceLogger.printStackTrace] java.lang.RuntimeException: Exception in Application start method
	at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:917)
	at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$1(LauncherImpl.java:182)
	at java.lang.Thread.run(Thread.java:750)
Caused by: java.lang.ExceptionInInitializerError
	at sun.awt.AppContext$2.run(AppContext.java:277)
	at sun.awt.AppContext$2.run(AppContext.java:266)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.awt.AppContext.initMainAppContext(AppContext.java:266)
	at sun.awt.AppContext.access$400(AppContext.java:135)
	at sun.awt.AppContext$3.run(AppContext.java:321)
	at sun.awt.AppContext$3.run(AppContext.java:304)
	at java.security.AccessController.doPrivileged(Native Method)
	at sun.awt.AppContext.getAppContext(AppContext.java:303)
	at javax.imageio.spi.IIORegistry.getDefaultInstance(IIORegistry.java:154)
	at javax.imageio.ImageIO.<clinit>(ImageIO.java:66)
	at org.tizen.device.manager.util.MacUtil.setDockIcon(MacUtil.java:51)
	at org.tizen.device.manager.Main.start(Main.java:167)
	at com.sun.javafx.application.LauncherImpl.lambda$launchApplication1$8(LauncherImpl.java:863)
	at com.sun.javafx.application.PlatformImpl.lambda$runAndWait$7(PlatformImpl.java:326)
	at com.sun.javafx.application.PlatformImpl.lambda$null$5(PlatformImpl.java:295)
	at java.security.AccessController.doPrivileged(Native Method)
	at com.sun.javafx.application.PlatformImpl.lambda$runLater$6(PlatformImpl.java:294)
	at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:95)
Caused by: java.lang.RuntimeException: Non-Java exception raised, not handled! (Original problem: Invalid parameter not satisfying: index < [_itemArray count])
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1817)
	at java.lang.Runtime.load0(Runtime.java:810)
	at java.lang.System.load(System.java:1088)
	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1934)
	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1838)
	at java.lang.Runtime.loadLibrary0(Runtime.java:871)
	at java.lang.System.loadLibrary(System.java:1124)
	at java.awt.Toolkit$3.run(Toolkit.java:1636)
	at java.awt.Toolkit$3.run(Toolkit.java:1634)
	at java.security.AccessController.doPrivileged(Native Method)
	at java.awt.Toolkit.loadLibraries(Toolkit.java:1633)
	at java.awt.Toolkit.<clinit>(Toolkit.java:1670)
	... 19 more

Did you see my previous response if it doesn’t work for you then you need to open a Developer Support Request

This is the best information I have.

Due to issues in the recent version of macOS Sonoma it will not be supported in the Tizen Studio until a planned release in spring of 2024.

There is a work around for those who are facing issue in launching Device Manager in macOS Sonoma, they can use following CLI commands for similar functionality.

  1. permit for install -

$ /tools/sdb devices
List of devices attached
emulator-26111 device t-1019-1

$ /tools/ide/bin/tizen install-permit -s emulator-26111
Install Permitted

  1. Install the app -

$ /tools/ide/bin/tizen install -s serial -n pkgname – <path to base dir of tpk/wgt>
e.g - $ /tools/ide/bin/tizen install -n org.tizen.basic-1.0.0-i386.tpk -s emulator-26101 – ~/workspace/basic/Debug

Note I have not tried this as I don’t have a Mac

Ron
Samsung Developer Relations

“Spring 2024” is here. Is there any set release date of the update yet?

1 Like

There is a Tizen Studio 5.6 available for download at Download | Tizen Developers

It fixes the problem with Device Manager.

I tested it on MacOs 14.4.1 and I can now launch Device Manager app, but I haven’t tested install-permit with a newly created certificate.

It works fine, tested it.