Getting exception for jogl for apple app store app.

Hi All,

I am getting the following exception on my Mac OS X for my Apple Store App (not released yet). I am thinking it is a sandbox entitlements issue but not sure. There was a similar problem with an Applet from Safari and it was "Fixed". I am using Maverics 10.9 with jogl 2.1.0build 2.1-b111-20131010 and it works fine from java web start. Any ideas? Here is the exception:

Warning: Catched Exception while retrieving temp base directory:
java.lang.RuntimeException: Could not determine a temporary directory
        at com.jogamp.common.util.IOUtil.getTempDir(IOUtil.java:1130)
        at com.jogamp.common.util.cache.TempFileCache.<clinit>(TempFileCache.java:80)
        at com.jogamp.common.util.cache.TempJarCache.initSingleton(TempJarCache.java:90)

Thanks!

adanecito, please use the very latest version, not something we released 6 months ago.

I have just looked at the source code:
https://github.com/sgothel/gluegen/blob/master/src/java/com/jogamp/common/util/IOUtil.java#L1387

All attempts of finding a temporary directory failed in your case. It seems that you aren't allowed to write in java.io.tmpdir or in the home directory.

Edit.: If you don't succeed in finding a workaround, disable the automatic extraction and loading of the native libraries (there's a flag to do that, look at the JOGL user's guide) and put the native libraries into your .app file or bundle.

Many thanks again for the prompt reply.
I am limited in regards to the jogl version by what is supported by WWJ. They did not support the latest version of JOGL due to some issues with Multi-Window support. I am not sure what that means but I will see if they now support the latest version of JOGL. If not I will ask them.
I have the native libraries on my app bundle already.
If needed I will try your workaround suggestion.

Best Regards,
-Tony

On 04/09/2014 05:26 PM, adanecito [via jogamp] wrote:
> Many thanks again for the prompt reply.
> I am limited in regards to the jogl version by what is supported by WWJ. They
> did not support the latest version of JOGL due to some issues with
> Multi-Window support. I am not sure what that means but I will see if they now
> support the latest version of JOGL. If not I will ask them.
> I have the native libraries on my app bundle already.
> If needed I will try your workaround suggestion if needed.
>

Bug 865 <https://jogamp.org/bugzilla/show_bug.cgi?id=865>,
fixed on 2013-10-23, reflects your Safari IOUtil temp-dir issue,
and in included in release 2.1.2 ( 2013-11-01 )
   <http://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.1.2>.

You can see, your build  'jogl 2.1.0 build 2.1-b111-20131010'
does not include this fix.

Latest release is 2.1.5 ( 2014-03-11 )
   <http://jogamp.org/wiki/index.php/SW_Tracking_Report_Objectives_for_the_release_2.1.5>

It might be helpful to establish some communication w/ the WWJ team,
namely Tom Gaskins and/or Patrick Hogan.

Cheers, Sven

> Best Regards,
> -Tony

Hi Sven,

I did talk to the WWJ team and thier latest release uses 2.1.4 which was a recent update.
Thanks for letting me know which version of JOGL added the fix that gives me confidense the issue will be fixed when I upgrade.

I will upgrade tonight and hopefully have success on my Standalone for the Mac OS X Mavericks.

I will update this message thread about the results.

Best Regards,
-Tony

On 04/09/2014 07:21 PM, adanecito [via jogamp] wrote: Great.

Since you mentioned issues not allowing them to update to 2.1.5 (?),
I recommend the WWJ team incr. communication via forum and bugzilla.

The next release will be 2.2.0, but it will take a while
and incl. API changes.

Note: A minor version number change implies API changes.

~Sven

Hi Sven,

That was 6 months ago but since they now are using Jogl 2.1.4 I am assuming they got past them. I did send them the link to Jogl 2.1.5 fixes/enhancements in case they want to upgrade again. With the amount of code they have to retest I suspect they do not upgrade very often but I could be wrong.

Best Regards,
-Tony

Hi Sven,

The issue was resolved when I upgraded to 2.1.4 of JOGL.

Thanks for the help.

-Tony

Why not upgrading to JOGL 2.1.5-01? Because of WWJ?