I definitely see this crashing issue in places where there are multiple call in a very short time. Earlier builds (I stepped back down to 919) do not exhibit the behavior. [import]uid: 96383 topic_id: 24299 reply_id: 126084[/import]
Build 919 was the first iOS 6.0 build and there is no real difference in the network.request code between that and the current build, 925. My guess is you were not seeing the problem with previous builds when you built for iOS5.1 and not iOS6.0. We believe this is iOS6.0 SDK issue and not because anything changed in Corona. (The network.request code has not changed in Corona in a long time.) [import]uid: 7559 topic_id: 24299 reply_id: 126085[/import]
Your bug report only mentioned the one bug so that’s what we fixed. Please reply to the email and mentioned the other issue and how it can be reproduced.
You need to reply through the bug reporting system and not on this API page. These pages are no longer used and all comments will soon be turned off and these pages will soon be removed.
You are free to post on the forums any bugs you find but realized we only work on bugs that are filed as bug reports AND include a description and project code to demonstrate the problem. You can post bug reports on the forum to make others aware of the issue and verify that the bug is valid.
Thanks,
Tom
[import]uid: 7559 topic_id: 24299 reply_id: 126311[/import]
@Tom
In my app
I call network.request three times at a very shot time.
so it’s reasonable to reproduce it using for loop.
my sample is using one button, just for u easy to recognize. u can make three 3 or more “network.request” with one click.
it would reproduce the status easier. [import]uid: 25057 topic_id: 24299 reply_id: 126088[/import]
@Tom
I have received one e-mail said that u have solved this bug.
Now network.request won’t crash apps.
“YES”, u did resolve this bug.Thanks
But not entirely.
I should mention there are two bugs out there actually.
One is “crash”(resolved)
One is “fail request”
When using network.request at very short time.
ex. request destinations are more than 2 URLs.
Some request will fail fetch.
it happened very often. even u have resolved “crash” issue.
It still exists.
I can’t wait for u to fix it again.
So i have tried to avoid it.
I have changed my code so
request in a very very short time => request in a row.
Like below
local function networkListener( event )
network.request( URL, "GET", networkListener2 ,params)
end
network.request( URL, "GET", networkListener ,params) Request one after one is exactly done.
But i do think u should resolve this bug , too.
Thanks [import]uid: 25057 topic_id: 24299 reply_id: 126304[/import]
Your bug report only mentioned the one bug so that’s what we fixed. Please reply to the email and mentioned the other issue and how it can be reproduced.
You need to reply through the bug reporting system and not on this API page. These pages are no longer used and all comments will soon be turned off and these pages will soon be removed.
You are free to post on the forums any bugs you find but realized we only work on bugs that are filed as bug reports AND include a description and project code to demonstrate the problem. You can post bug reports on the forum to make others aware of the issue and verify that the bug is valid.
Thanks,
Tom
[import]uid: 7559 topic_id: 24299 reply_id: 126311[/import]