Skip to content
This repository has been archived by the owner on Sep 6, 2019. It is now read-only.

Google Drive cannot open docs in its own format when Xprivacy is enabled #1209

Closed
treare opened this issue Jan 31, 2014 · 10 comments
Closed
Labels

Comments

@treare
Copy link

treare commented Jan 31, 2014

Since a few versions back (i don't know which) Google drive fails to open documents in it's own format. I could narrow this down to Xprivacy (nanadroid, uninstalled evrything else, then disabled xposed, afterwards enabled xposed and disabled Xprivacy). Drive is not restricted in any way nor are any system apps. For docs in other formats it asks which app to use and they can be opened. My second phone had an older Xprivacy and drive worked fine. Updated Xprivacy and same there: Google drive cannot open it's own docs anymore.

@M66B
Copy link
Owner

M66B commented Jan 31, 2014

Please enable debug logging in the XPrivacy settings and capture a logcat.

@M66B
Copy link
Owner

M66B commented Jan 31, 2014

I don't see anything unusual in the logcat you have sent me.
This problem is mostly caused by restricting the View category, especially android.intent.action.VIEW.

@treare
Copy link
Author

treare commented Jan 31, 2014

There is nothing restricted for google drive (or any other google and/or system app)

@treare
Copy link
Author

treare commented Jan 31, 2014

Also... with an older version it works perfect and after updating XP the problem was there. Nothing else was changed

@M66B
Copy link
Owner

M66B commented Jan 31, 2014

Did you try clearing XPrivacy data?
This will tell if there is a restriction or a bug in XPrivacy is causing this.
My best guess it is a restriction.
You might look into the usage data to find out which one.

@treare
Copy link
Author

treare commented Jan 31, 2014

Already looked at usage data. No restriction. Also not in general usage. Can i make a backup, clear data and restore without losing anything?Op 31 januari 2014 13:17, schreef Marcel Bokhorst:Did you try clearing XPrivacy data?
This will tell if there is a restriction or a bug in XPrivacy is causing this.
My best guess it is a restriction.
You might look into the usage data to find out which one.

—Reply to this email directly or view it on GitHub.

@M66B
Copy link
Owner

M66B commented Jan 31, 2014

You can make a backup and restore, but see the FAQ first for how too.
To be safe, also export XPrivacy settings.

@M66B
Copy link
Owner

M66B commented Jan 31, 2014

Maybe it is a firewall or add blocker app which prevents the document from opening.

@treare
Copy link
Author

treare commented Jan 31, 2014

99 percent its not the case. Ifi disable xprivacy it starts working again. I have no firwall appsOp 31 januari 2014 13:26, schreef Marcel Bokhorst:Maybe it is a firewall or add blocker app which prevents the document from opening.

—Reply to this email directly or view it on GitHub.

@M66B M66B closed this as completed in 66de1d9 Jan 31, 2014
@treare
Copy link
Author

treare commented Jan 31, 2014

Clearing data and restore wasnt helping. Its closed here. Error found?Op 31 januari 2014 13:57, schreef Marcel Bokhorst:Closed #1209 via 66de1d9.

—Reply to this email directly or view it on GitHub.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants