Android PHP SESSION ID

Solar2D Android
#21

Yes, that is a known issue on Android and Windows. It’s on our to-do list, but it’s low priority because this issue rarely comes up.

My point of view: I was quite surprised Apple’s Cocoa HTTP request APIs automatically cached cookies because most frameworks that I’ve used in the past make you do that yourself. On Windows and Android, we’ll have to write our own cookie handling code by looking at the HTTP response headers and persisting them to/from file. It’s not a small task.

As a work-around, you may want to use a web view instead where cookie support does support cookies and implement HTTP requests via JavaScript. That’s the only solution that I can think of at the moment. [import]uid: 32256 topic_id: 25630 reply_id: 139504[/import]

#22

Is something being done about this?

I can not build an app to android until cookie information is being saved. I’ve tested on several androids and they are giving the same behavior.

iOS has no issue. [import]uid: 30130 topic_id: 25630 reply_id: 139368[/import]

#23

cowbear,

We now have MapView support on Android. So, you don’t have to implement your own via a WebView. Please see sample app “Interface/MapView” that is included with the Corona SDK for an example on how to use map views on Android. [import]uid: 32256 topic_id: 25630 reply_id: 139373[/import]

#24

Oh sorry, I wasn’t being specific.

Cookie data is not being saved on android as stated by the topic creator. Every time I send a network.request API call on android to my web-server, the PHP Session ID is not being saved by the device and seems to forget it, leaving users unable to sign into their accoumt, and leaving me unable to build my app for android users.

I don’t have this issue on any iOS device, but I have tried on several android devices giving the same issue. [import]uid: 30130 topic_id: 25630 reply_id: 139484[/import]

#25

Yes, that is a known issue on Android and Windows. It’s on our to-do list, but it’s low priority because this issue rarely comes up.

My point of view: I was quite surprised Apple’s Cocoa HTTP request APIs automatically cached cookies because most frameworks that I’ve used in the past make you do that yourself. On Windows and Android, we’ll have to write our own cookie handling code by looking at the HTTP response headers and persisting them to/from file. It’s not a small task.

As a work-around, you may want to use a web view instead where cookie support does support cookies and implement HTTP requests via JavaScript. That’s the only solution that I can think of at the moment. [import]uid: 32256 topic_id: 25630 reply_id: 139504[/import]