Multi-Process Apps Result in TRANSACTION_URI Not Being Initialized about chuck HOT 11 OPEN

I, too, have run into this issue.

from chuck.

any solution on this?

from chuck.

Thanks! I half anticipated this would come up, by which point my use of ChuckContentProvider was well intrenched.

I'm inclined to just add a note to the docs saying this project is not suitable for multi-process apps, until I can determine if there is enough demand to make this effort worthwhile.

from chuck.

I am also running into this problem. I'm working on a simple SyncAdapter application, and was hoping to use Chuck for some network diagnostics. Looks like the issue is known, so I just wanted to add my name to the hat of affected users.

from chuck.

I am also running into this problem. I use another process to collect my app crash report and send it to server.

from chuck.

Just for feedback, I have also run into this problem.

from chuck.

I am running into this problem too. I start an webview in another process for memory leak from webview.

from chuck.

Workaround: TRANSACTION_URI can be initialized through reflection when necessary

Class clazz = getClass().getClassLoader().loadClass(
    "com.readystatesoftware.chuck.internal.data.ChuckContentProvider");
Field field = clazz.getField("TRANSACTION_URI");
(field.get(null) == null) {
    field.set(null, Uri.parse("content://" + context.getPackageName() +
        ".chuck.provider/transaction"));
}

from chuck.

Any updates on this issue ? Also run into this problem while using SyncAdapter

from chuck.

Hello! Any updates?

from chuck.

Quick update: this project has been forked https://github.com/ChuckerTeam/chucker
Please note that we removed the ContentProvider in chucker as we haven't found a great use case for that. If you have one, please open an issue on the fork and we re-implement it 👍

from chuck.