Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Error: Unexpected end of document" when blocking trackers #269

Closed
Bazoogle opened this issue Nov 16, 2023 · 5 comments
Closed

"Error: Unexpected end of document" when blocking trackers #269

Bazoogle opened this issue Nov 16, 2023 · 5 comments
Labels
bug Something isn't working error something crashed

Comments

@Bazoogle
Copy link

Bazoogle commented Nov 16, 2023

Describe the bug
When blocking trackers, either by going to Apps -> Selecting an App -> Trackers -> Selecting the "batch select" button in the top left -> Selecting block
OR
Using the new batch tracker block feature

Sometimes I will get an error popup at the bottom that says "Error: Unexpected end of document". When I used the batch tracker block for the first time, the message actually popped up like 20 times layered one over the other. But when I did them manually one by one, it would only happen once. It's inconsistent, and not easy to replicate. After the 20 messages popped up the first time with the batch block, I did the block a second time, and it did not pop up that time.
To Reproduce
Steps to reproduce the behavior:

  1. Go to Apps
  2. Select an App
  3. Click Trackers
  4. Select the "batch selection" icon in the top left
  5. Select block
  6. Error pops up in the bottom sometimes

OR

  1. Go to Batch
  2. Select all apps
  3. Click the nuclear "tracker" icon
  4. Select all trackers
  5. Block
  6. Error pops up in the bottom sometimes, potentially several times

Reproducing is, unfortunately, inconsistent. I think I sometimes noticed it with the play store app "AppSales" and a few others. It seems after the first time, it doesn't happen as often. I was able to get it to happen again by re-enable the trackers, clearing the app data for Inure, then trying again. Though I then tried to do that a second time, and it didn't happen that time.

Expected behavior
Error should not pop up, and all selected trackers should be blocked

Screenshots

image

Smartphone:

  • Device: Moto Edge 2021
  • OS: LineageOS 20 Android 13
  • Version: Build 65
@Hamza417 Hamza417 added bug Something isn't working error something crashed labels Nov 16, 2023
@Hamza417
Copy link
Owner

Do you use any other program to block app components?

@Hamza417
Copy link
Owner

Do you use any other program to block app components?

I ran the blocker several times and haven't been able to reproduce this problem, could you answer this?

@Bazoogle
Copy link
Author

Do you use any other program to block app components?

I am not using any other app to block trackers within an app. I previously used Warden, though I just did a clean install and didn't install Warden and only used Inure. I use AdAway to block it via hosts, so if that could interfere, then yes. If that's separate, then I don't use any other service.

I could try and recreate it once again and get a log. I tried enabling debugging and viewing logcat. Is there a way I can get a verbose log?

@Hamza417
Copy link
Owner

Hamza417 commented Nov 18, 2023

Added an error popup there. You can get an early release build from here and get the error log if any pops up.

Hamza417 added a commit that referenced this issue Dec 4, 2023
  - #269 - Updated charset settings for XML parser
Hamza417 added a commit that referenced this issue Dec 28, 2023
  - #269 - Same error should not be posted multiple times
Hamza417 added a commit that referenced this issue Apr 16, 2024
  // Fixed the crash on reading the file, I haven't tested on blocking
  // and unblocking yet but this should do now for testing
  // build beta
Hamza417 added a commit that referenced this issue Apr 17, 2024
  // More optimization
Hamza417 added a commit that referenced this issue Apr 17, 2024
Hamza417 added a commit that referenced this issue Apr 17, 2024
@Hamza417
Copy link
Owner

I've fixed everything related to this issue. You can get the beta APK from here for testing, and let me know here if you find any issues.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working error something crashed
Projects
None yet
Development

No branches or pull requests

2 participants