0.26 backward incompatibility

Our Android app has heavy use of coroutines. But after upgrade from 0.25.3 to 0.26.x, the code stopped working.

Sure, I know about new CoroutineScope and I’m definitely gonna refactor it to use that (no one wants 100 deprecation warnings, right) later, but I’d like to have it working first.

Our typical coroutine builder look like this: launch(UI, parent = job).

Are there some known incompatibilites? Something particular I should look for? I’ve already spent couple of hours on it and couldn’t find anything.

[qwwdfsad]

No changes in our code.

That’s probably the problem. For example, if you had following code:

launch {
  launch { // <- is invoked on outer launch scope
    // do something
  }
  // do something else 
}

after update it will behave diffrently, because launch defines its own scope. To preserve compatibility, rewrite is as

GlobalScope.launch {
  GlobalScope.launch {
  }
}

[Pitel]

Also, adding GlobalScope to each launch and async makes the app work with Courtines 0.30.

We’ll now of course start adding scopes, and see where it breaks.

Thanks for your help!