timed out errors on Android

@loyola - That would be great if I could get an APK to test, I don’t even need any of the code. I just need to get some clue when it happens.

I don’t have access to accounts, but you can send it to chris at coronalabs dot com.

That would be much appreciated.

Cheers

Hi,

The error has been captured (thanks @loyola for APK) and forwarded to Engineering. We will see what they say.

Cheers.

Hi Chris.
What’s the news on this? Did you manage to get to the bottom of the Android timed out errors?
I’m also really keen to update my Coronium instance to your newest version if you have news on that?
_____________________

This is a different issue but there’s a problem on iOS9… I’m getting this :

ERROR: network request failed: http://XXX.XXX.XX.X/1/code/createUser [-1022: The resource could not be loaded because the App Transport Security policy requires the use of a secure connection.]

( Where XXX.XXX.XX.X is my Coronium instance IP )
I’m guessing it’s an  iOS App Transport Security issue. I tried adding an entry in the build.settings to whitelist this but it seems we’re not allowed to add IP addresses as NSExceptionDomains.

NSAppTransportSecurity = { NSExceptionDomains = { ["XXX.XXX.XX.X"] = { NSIncludesSubdomains = true, NSExceptionRequiresForwardSecrecy = false, NSExceptionAllowsInsecureHTTPLoads = true, } }, },

Any suggestions on this?

I should probably start a new thread for this iOS9 ATS problem but for now I have two workarounds which are both not ideal …

  1. use **http://xip.io/**to provide wildcard DNS for my Coronium instance IP

  2. Add  NSAllowsArbitraryLoads = true to the NSAppTransportSecurity table in build.settings.

I’m concerned the first workaround will slow stuff down and compromise security and the second workaround will almost certainly cause Apple to reject my app. What do you suggest doing?

Hi,

Please start a new thread on Apple issue. Also be sure to understand the underlying changes that are happening everywhere right now.

https://developer.apple.com/news/?id=05042016a

Thank you for your patience. 

@develephant, thanks for the info.
I’ve moved this iOS9 Apple issue to a new thread. Please have a look if you get a moment :
https://forums.coronalabs.com/topic/63216-coronium-setup-and-ios-app-transport-security-policy/

Thanks again for your work and support on Coronium.

Hi,

What version does your control panel read, and where are you hosting?

Cheers.

Hi Chris. I guess it’s Beta 1.92 if the bottom left version is what’s to go by (?) …

Hi,

I’ve had no other reports of this issue specifically, and with what info you’ve provided it’s a little ambiguous what could be triggering the timeout. I would think about moving up to a more recent version.

Are you seeing anything in the error log?

cat /home/coronium/logs/error.log

Let me know.

Cheers.

Have you done a tutorial or some instructions on how to update to the latest version? I’m on DigitalOcean with 1.92.

There were some entries in the error.log but they seemed old so I cleared and re-saved it. I’m guessing that’s how you clear it right? Now none are coming up but the problem obviously persists. I’ll keep an eye on the log.

Hi.
I checked the error log and saw this today. Any idea what it means? Could this be my problem?

2016/03/30 22:20:18 [error] 10705#0: \*67981 access forbidden by rule, client: 95.45.254.121, server: , request: "GET /1/code/createUser HTTP/1.1", host: "104.236.57.1" 2016/03/30 23:29:38 [error] 10705#0: \*67982 access forbidden by rule, client: 86.47.80.146, server: , request: "GET /1/code/createUser HTTP/1.1", host: "104.236.57.1"

Also, would you be able to instruct me on how to update Coronium?
Cheers

Hi Julius,

What data storage are you using? Just Mongo? or MySQL as well?

I’ll put together some notes for moving to an updated version.

Cheers.

@develephant. Yea, it’s just Mongo I’m using.
If it helps you to help me, I’m happy to send you my server lua functions? I’d really appreciate getting past this bug.

Do you have any notes for me on moving to an updated Coronium version?

Cheers.

Hi,

For Mongo its pretty simple, you need to log in SSH and:

sudo mongodump -o mongo-coronium.bson

move the .bson file on the new box, import:

sudo mongorestore mongo-coronium.bson

You should then only need to move your cloud code.

Let me know if you run into any problems. I am fairly sure your error is permissions based. But that’s being addressed in the next release.

Cheers.

I’m having the same problem juliusbangert is having. Odd thing is that I am running another app, pointing to the same coronium server, and it connects no problem. iOS connects without a problem too. So does the simulator, no problem. But one of my apps gets a “timed out” error whenever it tries to connect with the android version of the app. I don’t see anything in the error report at /home/coronium/logs/error.log. 

Also, my permissions for android in build settings are:

"android.permission.INTERNET",
            “android.permission.ACCESS_NETWORK_STATE”,
            “android.permission.WRITE_EXTERNAL_STORAGE”,

I’m running Coronium 1.93.1.

Hi,

Can you let me know what your Corona Simulator version is?

Thanks.

Hi Chris.

I only just noticed your reply about doing a Coronium update, thanks. Please could you explain a bit more…

So far I have made an SSH connection to the Coronium server and run the following two commands after each other…

sudo mongodump -o mongo-coronium.bson

sudo mongorestore mongo-coronium.bson

 

Is that correct? What do I need to do next?

Will this fix the permissions based error you suspect is my problem?

I’m running Version 2016.2861 (2016.4.9).

Hi,

@julius - Do you mind sending me  your cloud file. I think I might have a lead on the issue (chris at coronalabs dot com). 

@loyola - Are you calling cloud code when you have the timeout issue?

Let me know.

Cheers.

@develephant. I’ve sent you the server lua files. Cheers.
__________________________________________________

With regards to the update; I just ran these two commands :

sudo mongodump -o mongo-coronium.bson

sudo mongorestore mongo-coronium.bson

Is that enough? Or was there something else I had to do? Restart server or something?