[quote=355041:@Kyryl Pekarov]Hi Kem,
Kaju 2.0 doesn’t support mac x64 bit?
Or am I missing something?[/quote]
It does. I use it in 64 bit. What gives you the impression that 64 bit isnt supported?
There is no 64bit binary for macos, the same in the code. I can’t find it.
We have 2 version - 32 and 64 bit builds.
is it possible to use Kaju to update 32bit and 64bit macos apps? Upgrade from 32bit to 64bit Macos?
What do you mean no 64 bit binary? Compile it yourself in 64 bit.
sorry, I wasn’t clear.
I mean to update macos 64bit app. There is no option to add 64bit macos binary to the Kaju Admin. Only Linux and Windows.
For MacOS everything needs to be 64 bit or just 32 bit basically. There is no reason to compile both 64 bit and 32 bit for MacOS as all current MacOS system builds are 64 bit unlike Windows or Linux.
If you do 64 bit builds for MacOS dont do a 32 bit build. Its redundant.
Just put the 64 bit build in the location in Kaju admin for the binaries.
What Jon said.
If you truly do need to compile a separate 32-bit Mac version, use a second admin file that outputs a different json file and have the 32-bit version point to that instead.
Thank you!
Hello Kem,
Any idea why I`m getting an 103 error ? I get the pref file and the update popup shows but when I press update to do the actual update , it gets stuck for a while then I get this error.
Thanks.
[quote=359004:@Aurelian Negrea]Hello Kem,
Any idea why I`m getting an 103 error ? I get the pref file and the update popup shows but when I press update to do the actual update , it gets stuck for a while then I get this error.
Thanks.[/quote]
Well that was weird, I just copied the URL and paste it on that pc browser, the app start to download, I cancel it and tried again and it started the update , so I have no idea why and how but it start to work now .
It seems that I`m getting some weird thing going on, so first of all , the app does not restart anymore once you press install and quit, then in the updates temp folder I get a folder called appname.exe-1 and one more called a–name.exe-tempfolder , those should be deleted or why there are 2 ? thanks
Do you set the App.UpdateInitiater property to Nil in App.Close?
Hi, yes I did, but I guess its something wrong with the pc settings, corporate provisioning, so even the update does not work some times, it gives that 103, which based on the docs means cannot reach or find the url if I`m right so I have no idea why .
What about those 2 folders ? I assume that one is for the previous version and one for the temp processing folder .
Thanks.
Yes, one is where the new version is downloaded and the other (if I recall) is for temp processing. You should be able to delete both safely.
Any known issues with 2017 R3?
I haven’t tried yet, but wouldn’t expect so.
hm…okay. getting some odd results back from the HTTPSocket but I’ll dig into it more today if I have the chance.
Even though I’ve set Redirect to true it’s not finding the correct address. A quick test in the Xojo framework shows that it brings it back the file contents as expected. So it appears that the redirect code isn’t working as expected. Very odd.
Man, I love this stuff
Looks like Kaju.HTTPSSocket.GetHeaders isn’t working the way it’s implemented. Always returns Nil (at least in R3).
That’s going to make things painful. Were you able to verify that outside of Kaju?