Corona now Solar2D
I am not sure if anyone looks at the forum anymore as there have not been any new post for over a year.
During the lock down I decided to alter my HAH android app.
Corona SDK has now been rebranded to Solar2D.
Now when I try and run my app I get a storyboard error.
Any help would be very much appreciated.
kema
Hi Brett
Would moving the server also be the cause of the firmware update being broken. I tried to update the firmware on one of my standby boxes the other day and got an error 404.
My box still trundles away and is also pretty stable.
Allan
Kind of - I accidently pointed the hah.dbzoo.com domain at the new server when I should have left it alone. I've deleted that DNS CNAME, give it 24hrs to propagate and the update functionality should be working again. Mind you there shouldn't be anything new to update to but it should tell you that at least.
My issue is that all the src code and build envrionment for the project is on a really old Centos 5.11 server. Github, where all the src is host, will no longer talk to this OS as the version of openssl used is so old. I have outstanding commits from the last change you got me to make that not on github.
I've got to a little bit of a dance to figure out what I changed and get this commited. From memory I updated curl and openssl to solve a twitter issue.
Hi Brett
Thanks for doing this, I updated my spare box this morning. It was still running firmware version 317 because it lives in a cupboard most of the time. The box which runs all the time is steady as a rock but probably wont go on forever!
Allan
The industry has educated people to expect a constant churn of features and bug fixes, with a project never being done, sadly this means if something hasn't been updated for a while we don't consider it worth using. Which is disappointing as there is a lot of code out there that is rock stable and doesn't need updating that's being ignored. This is such a project. I'm glad that its still humming along for you as stable as it ever was.
With the kernel being 2.4.17 I know in the year 2038-Jan-19 we'll have a problem with the 32-bit epoch overflow; you're good for a while yet.
At fate would have it I was poking about on the server and noticed email was not working. This got messed up last year when I moved the server and I never noticed. Sorry about that. I've not poked about with the Corona LUA stuff for a long time but I could probably figure out the problem.
Hopefull the forums send this out !
Editing message so I can make it send again now that email IS working.