Languages

Menu
Sites
Language
MAC - Tizen Installer IDE Hangs

To whom this may concern, I get the following error when I press Next after accepting on the EULA. Please see the error below. 

NON RELATED BUT IMPORTANT ISSUES I ALSO FOUND
1. My windows computer has high resolution, so when I tried to install on that computer I couldnt see the installation window content...I simply kept pressing Enter and got through the installation (didnt see the buttons or sub content).

2. My Tizen Gear watch is not recognized in the Connection Explorer when I open the IDE or plug it in...How can I fix this? Windows recognizes the device as storage but the IDE doenst see it.

jried-mac:Java jried31$ java -version

java version "1.6.0_65"

Java(TM) SE Runtime Environment (build 1.6.0_65-b14-466.1-11M4716)

Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-466.1, mixed mode)

jried-mac:Java jried31$ java -XstartOnFirstThread -Dorg.eclipse.swt.internal.carbon.smallFonts -jar InstallManager.jar

2015-04-05 22:09:24.103 java[98097:7646810] [Java CocoaComponent compatibility mode]: Enabled

2015-04-05 22:09:24.103 java[98097:7646810] [Java CocoaComponent compatibility mode]: Setting timeout for SWT to 0.100000

2015-04-05 22:09:24.285 java[98097:7646810] sun.misc.ServiceConfigurationError: javax.imageio.spi.ImageOutputStreamSpi: Provider com.sun.media.imageioimpl.stream.ChannelImageOutputStreamSpi could not be instantiated: java.lang.IllegalArgumentException: vendorName == null!

    at sun.misc.Service.fail(Service.java:120)

    at sun.misc.Service.access$200(Service.java:111)

    at sun.misc.Service$LazyIterator.next(Service.java:284)

    at javax.imageio.spi.IIORegistry.registerApplicationClasspathSpis(IIORegistry.java:190)

    at javax.imageio.spi.IIORegistry.<init>(IIORegistry.java:121)

    at javax.imageio.spi.IIORegistry.getDefaultInstance(IIORegistry.java:142)

    at apple.awt.CToolkit.registerDefaultServices(CToolkit.java:1346)

    at apple.awt.CToolkit.<init>(CToolkit.java:154)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

    at java.lang.Class.newInstance0(Class.java:357)

    at java.lang.Class.newInstance(Class.java:310)

    at java.awt.Toolkit$2.run(Toolkit.java:859)

    at java.security.AccessController.doPrivileged(Native Method)

    at java.awt.Toolkit.getDefaultToolkit(Toolkit.java:826)

    at java.awt.Toolkit.getEventQueue(Toolkit.java:1689)

    at java.awt.EventQueue.invokeLater(EventQueue.java:1078)

    at apple.awt.CToolkit.screenParametersChanged(CToolkit.java:1353)

    at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)

    at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Unknown Source)

    at org.eclipse.swt.widgets.Display.applicationProc(Unknown Source)

    at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)

    at org.eclipse.swt.internal.cocoa.NSApplication.nextEventMatchingMask(Unknown Source)

    at org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)

    at org.eclipse.jface.window.Window.runEventLoop(Window.java:825)

    at org.eclipse.jface.window.Window.open(Window.java:801)

    at org.tizen.installmanager.ui.InstallManagerWindow.main(InstallManagerWindow.java:1000)

    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)

    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

    at java.lang.reflect.Method.invoke(Method.java:597)

    at org.eclipse.jdt.internal.jarinjarloader.JarRsrcLoader.main(JarRsrcLoader.java:58)

Caused by: java.lang.IllegalArgumentException: vendorName == null!

    at javax.imageio.spi.IIOServiceProvider.<init>(IIOServiceProvider.java:59)

    at javax.imageio.spi.ImageOutputStreamSpi.<init>(ImageOutputStreamSpi.java:74)

    at com.sun.media.imageioimpl.stream.ChannelImageOutputStreamSpi.<init>(ChannelImageOutputStreamSpi.java:64)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)

    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)

    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)

    at java.lang.reflect.Constructor.newInstance(Constructor.java:513)

    at java.lang.Class.newInstance0(Class.java:357)

    at java.lang.Class.newInstance(Class.java:310)

    at sun.misc.Service$LazyIterator.next(Service.java:282)

    ... 31 more

Responses

2 Replies
Vikram

Hello,

Regarding your first issue, how about to change the resolution of your PC for installation only?

If you have extened display in PC, mayby you can change it to find the solutiuon.

And for second problem, please check this setting in your Gear 2.

  settings-->Gear Info -->USB debugging

But if you still observe same problem, you need to execute "sdb kill-server" and "sdb start-server" in the command prompt of PC.

Hope this will help.

 

Vikram

Pleaes refer to this description as well.

 

https://developer.tizen.org/downloads/sdk/installing-sdk/troubleshooting

 

    When Install Manager does not appear in Windows®

If the Install Manager does not appear, you should suspect trouble in JDK installation.
 You can check your problem by following directions

Run the Install-manager with the -help options.
./install-manager.exe -help


If you see the following message, Java libraries are not suitable to Java executables.
 "Registry key 'Software\JavaSoft\Java Runtime Environment\CurrentVersion' has value 'XXX', but 'XXX' is required."

The cause is that Java files in System32 do not match to Java Runtime Environment in registry.

To avoid this problem:
•Copy java.exe file to System32 directory.

If Tizen Emulator does not appear when you launch it, you may face the same trouble log at <TIZEN-SDK-DATA directory>/emulator/vms/<Emulator name>/logs/emulator.log file.