Widget inspector is not working

[Ramzes5614]

Hi! Thanks for the plugin!
There is an error with widget inspector. It does not start when the project has a custom ContentProvider.

On your example_provider it's also not working. How can we solve this problem?

@pragma('vm:entry-point')
void exampleContentProviderEntrypoint() {
  MyAndroidContentProvider(
    'com.nt4f04und.android_content_provider_example.MyAndroidContentProvider',
  );
}

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.84.2)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!```

[Ramzes5614]

@nt4f04uNd, We also tried to run on Flutter version 3.13. To no avail

[nt4f04uNd]

Hi

This is bug a in Flutter SDK
flutter/devtools#6640

When AndroidContentProvider is created, it first creates its own engine.
The engine for FlutterAcivity is created the after that, and is not picked up by flutter_tools (supposedly).
Therefore what you see in devtools is Flutter tree tied to AndroidContentProvider isolate (which doesn't draw anything).

I digged a bit, but I don't think there is an easy way to properly fix this on our side.

But there is a workaround for it, which you can use when you need to access devtools.

package com.nt4f04und.android_content_provider_example

import android.os.Handler
import android.os.Looper
import com.nt4f04und.android_content_provider.AndroidContentProvider

class MyAndroidContentProvider : AndroidContentProvider() {
    override val authority: String = "com.nt4f04und.android_content_provider_example.MyAndroidContentProvider"
    override val entrypointName = "exampleContentProviderEntrypoint"

    override fun onCreate(): Boolean {
        Handler(Looper.getMainLooper()).postDelayed({
            super.onCreate()
        }, 2000)
        return true
    }
}

Let me know if that works for you and I could put that into README

[YoungPotato]

Hi

This is bug a in Flutter SDK flutter/devtools#6640

When AndroidContentProvider is created, it first creates its own engine. The engine for FlutterAcivity is created the after that, and is not picked up by flutter_tools (supposedly). Therefore what you see in devtools is Flutter tree tied to AndroidContentProvider isolate (which doesn't draw anything).

I digged a bit, but I don't think there is an easy way to properly fix this on our side.

But there is a workaround for it, which you can use when you need to access devtools.

package com.nt4f04und.android_content_provider_example

import android.os.Handler
import android.os.Looper
import com.nt4f04und.android_content_provider.AndroidContentProvider

class MyAndroidContentProvider : AndroidContentProvider() {
    override val authority: String = "com.nt4f04und.android_content_provider_example.MyAndroidContentProvider"
    override val entrypointName = "exampleContentProviderEntrypoint"

    override fun onCreate(): Boolean {
        Handler(Looper.getMainLooper()).postDelayed({
            super.onCreate()
        }, 2000)
        return true
    }
}

Let me know if that works for you and I could put that into README

Thanks for the quick response.
It works. It's enough for the provider to be created asynchronously, while DevTools are initialized synchronously (not sure). So, you can skip the delay and use 0 instead of 2000