I’m wondering if Android is sensitive to the []'s in your GET key-value pairs. Normally non-letter/numbers have to be URL encoded. You can use a function like:
local function urlencode(str) if (str) then str = string.gsub (str, "\n", "\r\n") str = string.gsub (str, "([^%w])", function (c) return string.format ("%%%02X", string.byte(c)) end) str = string.gsub (str, " ", "+") end return str end
If you feel this is a bug, I encourage you to file a bug report. The bug report should contain a simple demonstration app that lets us build for device and run it and see the problem. Therefore it needs a main.lua, config.lua, build.settings, the actual URL’s you’re trying to access that causes the problem. Put the whole demo project in a .zip file and use the Report a Bug link at the top of the page.
You will get an email confirming the bug report. It will have a case ID number in the subject, please post that case ID number back here as a reference. I’ll grab the bug report and see if I can see the problem when I see your live production code. If it’s a bug, then it will be in the system. If not we will know the cause and you can proceed.
Has this issue been resolved? I’m facing probably a similar situation with our self hosted parse server. If there is a workaround would love to hear about it.
Want params are you use in your parse request? Basically what your request look like. Are you use the parse plugin via corona marketplace, making your own, or using mod_parse
Actually I tried both and got the same behavior on Android device. It’s a simple get request for parse users sorted by their XP value and limited to top 25. I don’t have it near me so can’t send the actual URL.
Ok I assumed this bug and you problem might be related because it way not working android and I just remembered this bug. But post the url when you get a chance.
I think you nailed it. Good catch as I did not see this thread. I will try to file a bug report end of next week when I’m back from our family vacation. I don’t understand how such a bug evaded the core team for so long. It seems a very basic behavior that many encounter. Unless there is some obvious workaround I’m not familiar with.
I’ve tried the new update of parse plug-in and still get the issue. I wondered since the plug-in uses native libs if it could have avoided the issue, but probably they use the default network lib by Corona, so the issue remains.
I’m not sure how the request is sent since there is no way to know what network.request compiles. However, the input to this method for example is: (users table assumes to have the following additional columns: xp,rank,play,win)
When sent via simulator, this returns exactly 7 entries, sorted by most XP. When sent via android device, this returns all entries in the table, unsorted.
Has this bug been fixed yet? A major feature in my application depends highly on this to work. I have successfully integrated Google Drive into my application, but multiple queries must be in the URL in order for it to work. My application is currently only available on Android, and I am looking to release this update in the next week for my customers. Please fix this ASAP!
I have a drive plugin on the way and it works fine. The big problem I believe was the way the url was written. If you have having trouble with this and you believe this is a bug then report it. The worst corona can say is it not a bug and explain why it is not a bug. https://developer.coronalabs.com/content/bug-submission