Project

General

Profile

Actions

Bug #961

closed

Crash trying to save text document if the system app that handles `android.intent.action.CREATE_DOCUMENT` is disabled

Added by Air Yes about 1 year ago. Updated almost 1 year ago.

Status:
Closed
Priority:
Next Release
Start date:
02/18/2023
Due date:
% Done:

0%

Estimated time:

Description

Starting versions 56-57 experience crashes sometimes clearly caused by some actions other times while simple browsing. Some data attached, let me know if anymore is needed. Now app is not usable.

Also after some time browsing bottom panel is not returning after hiding. Have to double click as if to toggle full screen to get it back.

Autofill keepass is not working. In tor browser it does e.g.


Files

PB about after 2 crashes feb18.23.txt (1.15 KB) PB about after 2 crashes feb18.23.txt Air Yes, 02/18/2023 02:06 AM
PB Crash in attempt to share logcat feb18.23.txt (2.23 KB) PB Crash in attempt to share logcat feb18.23.txt Air Yes, 02/18/2023 02:06 AM
PB logcat after 2 crashes feb18.23.txt (67.7 KB) PB logcat after 2 crashes feb18.23.txt Air Yes, 02/18/2023 02:06 AM
1.29.23 PB Crash.txt (1.46 KB) 1.29.23 PB Crash.txt Air Yes, 02/18/2023 02:06 AM
22.txt (5 KB) 22.txt Air Yes, 02/18/2023 02:06 AM
Privacy Browser 3.10.1 Logcat.txt (56.8 KB) Privacy Browser 3.10.1 Logcat.txt Air Yes, 02/18/2023 02:06 AM
PB Crash feb-28.23.txt (1.46 KB) PB Crash feb-28.23.txt Now my OS was somehow able to create the .txt Air Yes, 02/28/2023 07:44 PM
Actions #1

Updated by Soren Stoutner about 1 year ago

  • Subject changed from Multiple crashes to Crash trying to save text document
  • Assignee set to Soren Stoutner
  • Priority changed from 3.x to Next Release

Please file a separate bug report for each issue. I will address crashing here. If you would like to discuss autofilling keyboards, I would recommend you first contact the maker of that app and then possibly file a separate bug report here if you have any information that the problem is on Privacy Browser's side.

Regarding the crashes, the logs show two different problems, although they may be related. The first one is that `No Activity found to handle Intent { act=android.intent.action.CREATE_DOCUMENT typ=text/plain (has extras) }`. This basically means that your Android device doesn't know how to create a text document (probably meaning that attempting to save a text document to the file system fails because there is no file picker available). Are you using a custom ROM or have you somehow customized your device to disable a core Android feature?

Actions #2

Updated by Air Yes about 1 year ago

Again I'm not sire if this field works for reply as i don't see my previous attempts to reply here.

So 1st problem is lack of text document creation tool in my os. What is the second problem you see from the crash report?

Actions #3

Updated by Air Yes about 1 year ago

By the way my device is pixel 5 with grapheme os, not sire if this is considered stock or custom as i did not perform any modifications. Installed strictly by GOS's site instructions.

And just now i had another crash while switching apps, and crash report was successfully generated i copied it to clipboard no problem and was able to open it with text editor from that same dialog clocking share that before gave a crash by itself where you suspected that my OS cant create a .txt see attached.

Actions #4

Updated by Soren Stoutner about 1 year ago

The second error message in your logs is the following:

`java.lang.RuntimeException: android.os.TransactionTooLargeException: data parcel size 820728 bytes`

It isn't clear to me what the root cause of that error message. If it is different than not having disabled all apps that can act as a file picker (the easiest way to figure that out is to fix this problem and see if you still get that error) then you should open a new bug report as each bug report should only be about one subject.

Regarding not having a working file picker, have you disabled any system apps on your device? For example, the default file picker that ships with the AOSP (Android Open Source Project) is named Files (com.google.android.documentsui). I don't know if that is what Graphene ships or if they have replaced it with something else, but if you remove or disable all apps that perform the CREATE_DOCUMENT function, they you will end up with a broken Android that produces the error message you see in your logs.

Actions #5

Updated by Soren Stoutner about 1 year ago

  • Subject changed from Crash trying to save text document to Crash trying to save text document if the system app that handles `android.intent.action.CREATE_DOCUMENT` is disabled
Actions #6

Updated by Soren Stoutner about 1 year ago

  • Status changed from New to Feedback

Were you able to fix this by adding or enabling an app with the CREATE_DOCUMENT function?

Actions #7

Updated by Soren Stoutner almost 1 year ago

  • Status changed from Feedback to Closed

I am closing this bug report as I haven't heard back from the reporter and he likely was able to fix his problem by enabling the required part of the Android OS. If anyone has this problem and isn't able to fix it by enabling the app that handles `android.intent.action.CREATE_DOCUMENT`, feel free to leave a commend and I will open the bug back up.

Actions

Also available in: Atom PDF