[5.3.1p1] WWW.isDone hangs in iOS

No luck on Unity 3D 5.3.2 p2 @christophergoy , i have to replace WWWConnection.mm.Then its work. I can expect this issue will fix on Unity3D 5.3.2 p3. is it right?

 

@christophergoy i am using unity 5.3.2p2 and when calling www it is not gives me response but when i changed your mm class it worked. can you confirm that this is same bug ?

 

Does this error: "NETWORK_EVENT_DATA_STALL_AT_APP_LAYER" in xcode iOS device log has to do with this issue?

I get quite a lot of freezes that seem to revolve around WWW, but it's hard to tell where excatly.

 

The WWWConnection.mm does not fix my freeze case. So it's not related.

Just another fantastic show stopper related to anything unity 5.3...

Wow. Just wow. I've failed case 768390.

 

Hi @christophergoy
Glad to hear that - thanks.

Forgive me for getting cynical there, but I'm a long time Unity developer, and honestly Unity 5 and specifically now 5.3+ is the worst release Unity came up with. This affects the jobs and projects of huge number of people around the world and the jiggling needed to handle the Unity tech issues are causing people to waist weeks of works on the tool instead of on the content which is the exact opposite of what Unity should be about. It's getting to a point where I'm not sure Unity should be used as a cross-platform game development tool because it can't handle the technical changes fast enough.

I'm not claiming this is any easy task for you! but is Unity sure this wonderful cross-platform tool can really keep being what it was?

 

@christophergoy I'm sure you are! thanks again.

By the way - once you do solve the issue I have stumbled upon, if it will be just a code replacement such as the file you've posted before, could you post it prior to the patch/release? The reasoning is testing earlier and knowing whether I can wait for an upcoming patch or do I have to rollback to 5.2.3 (this might be something unity should consider to enable on general bases).

 

Hey, we just faced this issue (FB images fail to download) after we upgraded to 5.3.2... The WWWConnection.mm file attached here seems to work for us. Awaiting an official fix.

Can anyone comment how can such a major issue make its way into an officially released version? it's VERY HARD for us to trust any new versions of the engine and makes upgrading very very difficult.

 

I second that - I think we all would want to know some strategic project management update is in the works in order to avoid such issues for future releases. It's been ~two month into 5.3+ and too many people can not upgrade yet, or even worse need the upgrade and are running after their tail hoping the update is working only to find out its not - and rolling back (it's a cross-platform - in our case we need to test 3 platforms x different devices/browsers x different os versions!!!!).

By the way - project management-wise while it is never a good idea to try an update on its early days, if you don't try that once in a while, an issue you might have might never be known to you guys in Unity. After the last couple of month with Unity 5.3+ I am positive many people are saying - "I'm not upgrading until 'everyone' says the upgrade is working", so less and less people will update Unity about bugs, making the future upgrades even worse!

Only by a strategic change, can Unity change this for the better.

 

I think that it's ABSOLUTELY MANDATORY to test versions as early as possible ! so at least you have a basic concept of whether things are working or not.
Also, the major problem (for me) is that you have no idea when upgrading, what things are currently broken. This means that it's a trial and error effort.

 

@christophergoy BTW - for such an issue i think it should be fairly simple to write a set of tests that will verify this scenario.

You could set up a local HTTP server (.NET already has all the classes in place for that) that will be configured to return fake responses (e.g: redirect, 404, 200, 500, etc). Each test will configure this server class with the expected result and will run a WWW coroutine against it to see if it completes, responds with the expected output, etc..

This shouldn't be that hard, and from what i've been reading it looks like you have a test framework that executes on devices, so you could run that on iOS devices to gather the results. I think this is a must, if not already done.

 

@christophergoy so is 5.3.2p4 coming?

 

@christophergoy half a day after last day but there doesn't seem to be an update...

 

Lucky for us it's not Friday the 13th

 

@christophergoy thanks for the update mate.

Our initial tests look good (iOS, Android and WebGL). Hope we won't bump into more surprises.
Do note there still seem to be issues with the sprite packing. Many times I need to clear the sprite atlases folder after switching platforms to fix an issue that makes the builds include extra size and make some textures or shaders corrupt in the build (I get black areas and bad fonts at certain areas).

 

wow, I feel like an idiot.. I just spent 6 hours trying to debug this problem on iOS using 5.3.2p2.. thinking the entire time it was something I was doing wrong, but nope... found this and presto works like a charm.

There has got to be a better way to deal with these kinds of issues for us.. how am I to know that if I'm using 5.x.x version of Unity on iOS X.X with xCode X.X, that a little thing like this will cost me hours of head banging frustration and code rework.

argh!.. @$^@%&WSDFG

 

haha, I know man... someone please smack me. But I almost "always" think.. "this is my fault, what did I do wrong"

 

@christophergoy meet the same problem in 5.3.7 / 5.3.4 / 5.3.6, can't believe this thread is created over a year!
I'm gona try your script, hope it works.

@christophergoy I see the WWWConnection.mm of 5.3.7p4 has already merge most of your fixed script in compare with the one of 5.3.0. But the bug still existed. I can't repo that in a steady way, but it will certainly happen sooner or later, and when that happened, the log shows all the WWW.isdone remains false forever. And I've been remove all the WWW.Dispose long time ago. Any thoughts on that?

 

Thank god, I'm counting on you! We've test our game online for several month on Android, and finally ready to publish for both Android and iOS these days, now we've been stalled by this issue for nearly a week. It's there a new script of WWWConection.mm that can fixed this issue, we may won't be able to wait for next patch release. Really appreciated!

 

o m
so much thanks to u chris! currently we roll back to 5.3.2p4 which certainly fixed that issue. gona try merge your script tomorrow, after all, later is better

UPDATE: @christophergoy I've merged the file into 5.3.7p4 and everything goes well for now. I guess it's solved!

 

Hi @christophergoy, I still have this issue while loading resource from streamingassets by WWW on many version of Unity ex: 2017.3, 2017.2.2f1. It hangs at isDone that always be false and no error

 

Hi @Aurimas-Cernius is there a temporary solution to the issue? Almost every version of Unity 2017 has this issue includes 2017.4. However we cannot rollback to Unity 5 due to serval other issues of Unity. The crash and freeze of WWW, UnityWebRequest is dragging our user retention rate down and get lots of customer complains. Plz help thank you @@

 

as a workaround, can you avoid using isDone and use other properties (like progress) to see if download completes ?

 

@liortal Actually not only this issue, include others such as https://fogbugz.unity3d.com/default.asp?1020451_tjom5fclu25evsg2

Now I change all WWW and UnityWebRequest by BestHttp and everything seems work fine currently.