Btukfyl

I've got a music player which attempts to start a Service in onResume() of an Activity. I've removed a few lines for clarity, but the code is effectively:

@Override

protected void onResume() {

    super.onResume();



    startService(new Intent(this, MusicService.class));

}

According to the crash logs, this is throwing an Exception on some devices running Android P:

Caused by java.lang.IllegalStateException: Not allowed to start service Intent { cmp=another.music.player/com.simplecity.amp_library.playback.MusicService }: app is in background uid UidRecord{6a4a9c6 u0a143 TPSL bg:+3m25s199ms idle change:cached procs:1 seq(1283,1283,1283)}

       at android.app.ContextImpl.startServiceCommon(ContextImpl.java:1577)

       at android.app.ContextImpl.startService(ContextImpl.java:1532)

       at android.content.ContextWrapper.startService(ContextWrapper.java:664)

       at android.content.ContextWrapper.startService(ContextWrapper.java:664)

       at com.simplecity.amp_library.utils.MusicServiceConnectionUtils.bindToService(SourceFile:36)

       at com.simplecity.amp_library.ui.activities.BaseActivity.bindService(SourceFile:129)

       at com.simplecity.amp_library.ui.activities.BaseActivity.onResume(SourceFile:96)

How is it possible that my app is in the background, immediately after onResume() (and super.onResume()) is called?

This doesn't make any sense to me. Could this be a platform bug? All 162 users affected by this crash are on Android P.

We're testing this out right now which so far seems to be working. Will update as we see more results

class ResumingServiceManager(val lifecycle: Lifecycle) : LifecycleObserver {



    init {

        lifecycle.addObserver(this)

    }



    val disposable: CompositeDisposable = CompositeDisposable()



    fun startService(context: Context, intent: Intent) {

        if (Build.VERSION.SDK_INT < Build.VERSION_CODES.O) {

            context.startService(intent)

        } else {

            Single.just(true)

                    .delaySubscription(300, TimeUnit.MILLISECONDS)

                    .subscribeOn(AndroidSchedulers.mainThread())

                    .observeOn(AndroidSchedulers.mainThread())

                    .subscribeBy(

                            onSuccess = {

                                context.startService(intent)

                            }



                    ).addTo(disposable)

        }

    }



    @OnLifecycleEvent(Lifecycle.Event.ON_STOP)

    fun stopped() {

        disposable.clear()

    }



    @OnLifecycleEvent(Lifecycle.Event.ON_DESTROY)

    fun destroy() {

        lifecycle.removeObserver(this)

    }

}

In onCreate() initialize it and then anytime you want to start a service in onResume just call resumingServiceManager.startService(this, intent)

It's lifecycle aware so it will clear the disposable if it pauses cancelling the onSuccess from triggering when it might be on the way to the background with an immediate open/close.

use

startForegroundService(intent);

instead of

startService(intent);

try this it should work

if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {

    context.startForegroundService(intent);

} else {

    context.startService(intent);

}

and in onCreate() method of your service:

startForeground(1,new Notification());

hope it work for you

Maybe android.arch.lifecycle could be used as a workaround for this Android 9 bug?

public class MyActivity extends Activity implements LifecycleObserver {



    protected void onResume() {

        if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.O) {

            if (ProcessLifecycleOwner.get().getLifecycle().getCurrentState().isAtLeast(Lifecycle.State.RESUMED)) {

                startService(intent);

            } else {

                ProcessLifecycleOwner.get().getLifecycle().addObserver(this);

            }

        } else {

            startService(intent);

        }

    }





    @OnLifecycleEvent(Lifecycle.Event.ON_RESUME)

    void onEnterForeground() {

        startService(intent);

        ProcessLifecycleOwner.get().getLifecycle().removeObserver(this);

    }

}

I've found it here.