App does not open, showing a black screen

MinekPo1 commented 4 months ago

Checklist

[X] I am able to reproduce the bug with the latest version.
[X] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
[X] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
[X] This issue contains only one bug, that only occurs in Squawker

Affected version

v3.7.5 installed via github release

Steps to reproduce the bug

Open app

Expected behavior

The app opens normally

Actual behavior

There is a black screen

Screenshots/Screen recordings

N/A

Logs

Since the app does not open nor crash, logs are taken from logcat

1708674356.888 10580 23401 23401 E org.ca.squawke: Not starting debugger since process cannot load the jdwp agent.
1708674357.161 10580 23401 23421 E QT      : [QT]file does not exist
1708674357.326 10580 23401 23401 E org.ca.squawke: Invalid ID 0x00000000.
1708674357.514 10580 23401 23423 E ion     : ioctl c0044901 failed with code -1: Invalid argument
1708674357.843 10580 23401 23422 E flutter : [ERROR:flutter/runtime/dart_vm_initializer.cc(41)] Unhandled Exception: type 'Null' is not a subtype of type 'String' in type cast
1708674357.843 10580 23401 23422 E flutter : #0      xPa.wMf (Cei:59)
1708674357.843 10580 23401 23422 E flutter : <asynchronous suspension>
1708674357.843 10580 23401 23422 E flutter : #1      main (Bfi:234)
1708674357.843 10580 23401 23422 E flutter : <asynchronous suspension>
1708674357.491 10580 23401 23418 E OpenGLRenderer: EglManager::makeCurrent mED = 0x1, surface = 0x0, mEC = 0xb400007bc4b78ee0, error = EGL_SUCCESS

Affected Android/Custom ROM version

Android 12, mostly AOSP, with slight vendor modifications

Affected device model

Motorola e22

Additional information

My device has a firewall set up, but ~~I am unable to confirm or deny that any requests have been blocked.~~ no requests have been blocked.
I have manually manipulated the "twitterTokens" list
I have previously experienced #208 (though I believe I removed the affected accounts)

MinekPo1 commented 4 months ago

I've managed to look at the firewall logs, a single request to api.github.com is made.

MinekPo1 commented 4 months ago

I deleted the apps data, which removed the issue. I doubt I will be able to reproduce it without reinstalling an old version of the app

alanpoulain commented 4 months ago

Same issue here, maybe it's because of the change in guest accounts?

j-fbriere commented 4 months ago

I've managed to look at the firewall logs, a single request to api.github.com is made.

This is the verification for an updated version of Squawker. I know that you say that no request has been blocked. Do you mean all Twitter/X requests or all possible requests? Is the request to GitHub, api.github.com blocked by the firewall?

MinekPo1 commented 4 months ago

I've managed to look at the firewall logs, a single request to api.github.com is made.

This is the verification for an updated version of Squawker. I know that you say that no request has been blocked. Do you mean all Twitter/X requests or all possible requests? Is the request to GitHub, api.github.com blocked by the firewall?

As far as I remember, no requests to Twitter/X have been made, the request to Github was not blocked

MinekPo1 commented 4 months ago

by the way, I've tracked down there flutter/runtime/dart_vm_initializer.cc(41), unfortunately it is just a error raising line

j-fbriere commented 4 months ago

Actually the following 2 lines from your logcat tells a lot: Unhandled Exception: type 'Null' is not a subtype of type 'String' in type cast 1708674357.843 10580 23401 23422 E flutter : #0 xPa.wMf (Cei:59) I have done some reverse engineering of the libapp.so file from this version of the Squawker application apk in release mode. After a lot of digging I have discovered that the error is raised at the very start when the app is loading the authenticated tokens and the account profiles and that there were/are some null fields in your Squawker database records that are not supposed to be. I will add some more safe guards to make sure that those type of database records are null fool proof, even in case of some unattended manipulations (in the file to import for instance).

Thank you for having provided your logcat excerpt.

j-fbriere commented 4 months ago

Version v3.7.6 fixes this issue.

alanpoulain commented 4 months ago

It works again, thank you!

j-fbriere / squawker