hmhmmm not sure if this is a browser issue @hunterlester or an issue with jams and 32bit @Nigel … in any case it will be realted to the 32bit i would assume because everything works fine here with 64bit standard safe
It’s all good. This kind of feedback is highly coveted because it’s easy to become familiar with the setup process and forget about all the challenges that new people experience.
Thank you for taking the time to play with our software.
I’ll boot up my vm and see what’s going on over there. Hopefully I can see a bit of the Jams source code to find out what is immediately being called by native library.
Just curious what browser version is being used? I haven’t tested on any of the newer versions of either browsers. At the time I recommended Peruse 0.4.1. I think it could be because of running 32-bit. I haven’t tested with 32-bit but I’ll look into it.
When building the app we’ve had Safe browser 0.7.0 crash in mock but that was all fixed. Bryan will be doing code cleanup in a few weeks after some other stuff is finished and I’ll see if he can test 32-bit with the app to make sure it works fine.
[UPDATE]
By the way, I can initialise and authorise an app with the API playground at safe://codeplay.discover/ with no problem but if I navigate to any other site on Alpha2 that requires my client to download over a certain amount of data, I get the same exact crash. @Nigel This isn’t an issue unique to Jams.