Backlog issueshttps://gitlab.e.foundation/e/backlog/-/issues2022-01-28T08:21:44Zhttps://gitlab.e.foundation/e/backlog/-/issues/1053Issue with APPS - while searching for an app2022-01-28T08:21:44ZRalph BöhlkeIssue with APPS - while searching for an app- /e/ version: beryllium-pie-20200310
- Device model: Pocophone
- When it started to occur: noticed only today
## Summary
there is a tiny misbehaviour when searching for an app in the built-in app store
- While typing in the search b...- /e/ version: beryllium-pie-20200310
- Device model: Pocophone
- When it started to occur: noticed only today
## Summary
there is a tiny misbehaviour when searching for an app in the built-in app store
- While typing in the search bar from APPS a search query, there are already app names listed who start with the letters in the query. Example when I am typing "telegram", there is already a list of apps showing that start with the letters "telegram....".
- When II am selecting one from this list, let's say "Telegram X", I receive an error notification "App not found"
- when looking carefully in the search bar, there's written the name of the app I just selected - Telegram X. But there is a SPACE-character following the app name. In our example "Telegram X ".
- When I delete the SPACE and press <RETURN> on my keyboard, the installation page within APPS for Telegram X appears correctly.
So in brief when the user is choosing for list of similar named apps, the /e/appstore is adding always and empty space after the search term, this leads to an error message and the app in question cannot be found.
It would be good if a SPACE-character in the end of an app name is automatically deleted/ignored by APPS.
<Please tick one of the following sentences if relevant>
**Relevant screenshots**
![96_spaceANDerror-1](/uploads/27ef0067852c910beeb98c03b8419bb7/96_spaceANDerror-1.jpg)
![96_spaceANDerror-2](/uploads/9f127bd1e8e7cdcb158a2e6ea96ef5f2/96_spaceANDerror-2.jpg)Jalon-JabugoDayona Josephdayonajsph8@gmail.comDayona Josephdayonajsph8@gmail.comhttps://gitlab.e.foundation/e/backlog/-/issues/198Unable to save birthdays for contacts on local phone account2020-05-12T19:19:11ZMarkusUnable to save birthdays for contacts on local phone account## Summary
When I try to save a contact on the Local phone account, then I am unable to specify the birthday.
This problem does not appear when I select a "/e/ Address book" or a nextcloud powered "WebDAV Address book" for storing the c...## Summary
When I try to save a contact on the Local phone account, then I am unable to specify the birthday.
This problem does not appear when I select a "/e/ Address book" or a nextcloud powered "WebDAV Address book" for storing the contact.
## Steps to reproduce
1. Start the contacts app
2. Click on the "create new contact"-icon
3. Click on "Saving to"
4. Select "Local phone account"
5. Click on "More fields"
## What is the current behavior?
There does not appear an entry field for the birthday.
## What is the expected correct behavior?
I would expect that I am able to specify a birthday for a contact.Jalon-JabugoSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/1070apps are not up-to-date again2020-04-28T12:45:18ZRik Viergeverapps are not up-to-date againplease see https://gitlab.e.foundation/e/management/issues/910#note_35807
i'd like to re-open this issue. apps in the app store are lagging again.
Examples:
* Firefox: 6 march in Aurora, 29 jan in /e/ app store
* Facebook: 16 march i...please see https://gitlab.e.foundation/e/management/issues/910#note_35807
i'd like to re-open this issue. apps in the app store are lagging again.
Examples:
* Firefox: 6 march in Aurora, 29 jan in /e/ app store
* Facebook: 16 march in Aurora, 30 jan in /e/ app store
Strangely, other apps are MORE up-to-date in /e/ than in Aurora, such as Whatsapp.Jalon-JabugoNivesh Krishnanivesh@e.emailNivesh Krishnanivesh@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/448Protonmail app not working in OnePlus 22020-04-27T19:15:45ZJoan AbadProtonmail app not working in OnePlus 2# <Issue title>
## Summary
The Protonmail app, although being in the default app store, it's not working on a OnePlus 2 device. It just throws an "Protonmail stopped working" dialog.
I'm using the 0.7-2019071316537 nightly and tried to...# <Issue title>
## Summary
The Protonmail app, although being in the default app store, it's not working on a OnePlus 2 device. It just throws an "Protonmail stopped working" dialog.
I'm using the 0.7-2019071316537 nightly and tried to download the app in the /e/ store and from Aptoide with the same results.
## Relevant logs and/or screenshots
adb logcat: https://pastebin.com/n5KhUCYg
Thanks in advance.Jalon-JabugoSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/1047Search bar visible when editing app grid2020-04-27T19:12:15ZRomain HunaultSearch bar visible when editing app grid* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug ...* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
When you try to move an icon to the dock, the search bar can appears at the bottom of the screen.
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Install the /e/ test build by updating a previous version
1. From the launcher, enter in editing mode by long pressing an app icon
1. Try to move an app icon to the dock
**What is the current behavior?**
<What actually happens>
The search bar appears at the bottom of the screen
**What is the expected correct behavior?**
<What you should see instead>
The search should not appear in editing mode.
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
![screenrecord_20200309_10_29_05](/uploads/0e397e9843565fd7004210d80300dda3/screenrecord_20200309_10_29_05.mp4)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>Jalon-JabugoDayona Josephdayonajsph8@gmail.comDayona Josephdayonajsph8@gmail.comhttps://gitlab.e.foundation/e/backlog/-/issues/1046Icon disappear2020-04-27T19:12:15ZRomain HunaultIcon disappear* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug ...* /e/ version: /e/ test hobart
* Device model: kiwi (nougat)
* When it started to occur: both on fresh install and after update
* Reproducible with the last /e/ version: -
* Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Install the /e/ test build by updating a previous version
1. From the launcher, try to move icons
**What is the current behavior?**
<What actually happens>
1. Sometimes, the icon we try to move disappears
1. The icon is still visible when we try to edit the app grid
**What is the expected correct behavior?**
<What you should see instead>
1. The icon is not hidden
## Technical informations
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
```
```
**Relevant screenshots**
<Screenshots of the problem>
Below the Browser app is missing.
![screenrecord_20200309_10_41_56](/uploads/328c1ceec45ed66b966e522a908c6980/screenrecord_20200309_10_41_56.mp4)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
- Restart the device
- Restart BlissLauncher
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>
Similar to https://gitlab.e.foundation/e/apps/BlissLauncher/issues/32Jalon-JabugoAmit Kumaramitkma@e.emailAmit Kumaramitkma@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/1033Disable Reverse Lookup2020-04-27T19:09:42ZRomain HunaultDisable Reverse Lookup## Summary
<Summarize the improvement briefly and precisely>
**This improvement concerns** <Tick at least one of the following choices>
- [ ] UI
- [ ] Behavior
- [x] Privacy
## Description
**What is the current behavior?**
<What act...## Summary
<Summarize the improvement briefly and precisely>
**This improvement concerns** <Tick at least one of the following choices>
- [ ] UI
- [ ] Behavior
- [x] Privacy
## Description
**What is the current behavior?**
<What actually happens>
The **reverse lookup** setting is enabled by default in the Dialer
**What is the improved behavior?**
<What you should see instead>
The **reverse lookup** setting is disabled by default
**What does it bring?**
Privacy (don't send data to a third party by default)
<Why this improvement is needed>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
Install /e/ and check that **reverse lookup** is disabled by default, inside Dialer Settings.
Ideally, it should also be disabled after an update.
FYI @arnauvp @gaelJalon-JabugoMohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/876Issue after changing the e.account password2020-04-27T19:09:37ZRalph BöhlkeIssue after changing the e.account passwordI figuered out an issue when changing the password for my e.account.
- The e.account serves as email address and at the same time to authenticate myself within the e.cloud.
- When I want to change the password for an e.account, I need t...I figuered out an issue when changing the password for my e.account.
- The e.account serves as email address and at the same time to authenticate myself within the e.cloud.
- When I want to change the password for an e.account, I need to do that via https://ecloud.global/login?clear=1 (-> forgot password). Once the password is changed, I can easily login via a web browser to the account.
The issue I faced on my phone that was already running /e/OS.
- As the password was changed I received a notification for the /e/mail app "authentification failed". I clicked on the notification, typed-in the new password and was enabled right away to use the e.mail again.
- Within a few minutes (less then 5) the authentification error was popping up again on the phone and I need to retype the new password. Then again after some time the same the authentification error again....
- It seems that after some time the password is taken over from my e.account the phone was registered with. The principal e.account on the phone seems not to notify the user that the password is wrong and needs to be changed.
The correct behaviour would be that not the email app is notifying the authentification error but the principal e.account on the phone. The user should be enabled to modify the password there easily. This new password should be handed over to the email app automatically.
Hope this description is understandable.Jalon-JabugoSumit PundirSumit Pundirhttps://gitlab.e.foundation/e/backlog/-/issues/875Issue when renaming "contacts" or with additional address books2020-04-27T19:09:36ZPrateesh Issue when renaming "contacts" or with additional address booksI imported contacts directly to the e account by logging into my account on the computer and importing the vcard. But it didn't sync with my phone so I downloaded the vcard to my phone and imported them to the contact. Now I keep getting...I imported contacts directly to the e account by logging into my account on the computer and importing the vcard. But it didn't sync with my phone so I downloaded the vcard to my phone and imported them to the contact. Now I keep getting the notification from Account Manager saying HTTP server error - HTTP 404. Following is the debug log
```
--- BEGIN DEBUG INFO ---
Account name: Contacts (prateesh@e.email Eg)
Authority: com.android.contacts
HTTP REQUEST:
Request{method=PROPFIND, url=https://ecloud.global/remote.php/dav/addressbooks/users/prateesh@e.email/contacts/, tags={}}
<?xml version='1.0' encoding='UTF-8' ?><propfind xmlns="DAV:" xmlns:CAL="urn:ietf:params:xml:ns:caldav" xmlns:CARD="urn:ietf:params:xml:ns:carddav"><prop><CARD:supported-address-data /><supported-report-set /><n0:getctag xmlns:n0="http://calendarserver.org/ns/" /><sync-token /></prop></propfind>
HTTP RESPONSE:
Response{protocol=h2, code=404, message=, url=https://ecloud.global/remote.php/dav/addressbooks/users/prateesh@e.email/contacts/}
<?xml version="1.0" encoding="utf-8"?>
<d:error xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns">
<s:exception>Sabre\DAV\Exception\NotFound</s:exception>
<s:message>Addressbook with name 'contacts' could not be found</s:message>
</d:error>
REMOTE RESOURCE:
https://ecloud.global/remote.php/dav/addressbooks/users/prateesh@e.email/contacts/
EXCEPTION:
foundation.e.dav4android.exception.NotFoundException: HTTP 404
at foundation.e.dav4android.DavResource.checkStatus(DavResource.kt:408)
at foundation.e.dav4android.DavResource.checkStatus(DavResource.kt:392)
at foundation.e.dav4android.DavResource.processMultiStatus(DavResource.kt:484)
at foundation.e.dav4android.DavResource.propfind(DavResource.kt:379)
at foundation.e.accountmanager.syncadapter.ContactsSyncManager$queryCapabilities$1.invoke(ContactsSyncManager.kt:134)
at foundation.e.accountmanager.syncadapter.ContactsSyncManager$queryCapabilities$1.invoke(ContactsSyncManager.kt:79)
at foundation.e.accountmanager.syncadapter.SyncManager.useRemote(SyncManager.kt:781)
at foundation.e.accountmanager.syncadapter.SyncManager.useRemoteCollection(SyncManager.kt:802)
at foundation.e.accountmanager.syncadapter.ContactsSyncManager.queryCapabilities(ContactsSyncManager.kt:132)
at foundation.e.accountmanager.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:122)
at foundation.e.accountmanager.syncadapter.SyncManager$performSync$1.invoke(SyncManager.kt:59)
at foundation.e.accountmanager.syncadapter.SyncManager.unwrapExceptions(SyncManager.kt:807)
at foundation.e.accountmanager.syncadapter.SyncManager.performSync(SyncManager.kt:113)
at foundation.e.accountmanager.syncadapter.EeloContactsSyncAdapterService$ContactsSyncAdapter.sync(EeloContactsSyncAdapterService.kt:97)
at foundation.e.accountmanager.syncadapter.SyncAdapterService$SyncAdapter.onPerformSync(SyncAdapterService.kt:83)
at android.content.AbstractThreadedSyncAdapter$SyncThread.run(AbstractThreadedSyncAdapter.java:321)
SOFTWARE INFORMATION
Package: foundation.e.accountmanager
Version: 2.0.5-ose (248) from 2 Oct 2019
Installed from: APK (directly)
JB Workaround installed: no
CONNECTIVITY (at the moment)
Active connection: WiFi, CONNECTED
CONFIGURATION
Power saving disabled: yes
android.permission.READ_CONTACTS permission: granted
android.permission.WRITE_CONTACTS permission: granted
android.permission.READ_CALENDAR permission: granted
android.permission.WRITE_CALENDAR permission: granted
org.dmfs.permission.READ_TASKS permission: granted
org.dmfs.permission.WRITE_TASKS permission: granted
System-wide synchronization: automatically
Account: prateesh@e.email
Address book sync. interval: 15 min
Calendar sync. interval: 2 min
OpenTasks sync. interval: 2 min
WiFi only: false
[CardDAV] Contact group method: GROUP_VCARDS
[CalDAV] Time range (past days): 90
Manage calendar colors: true
Address book account: Contacts (prateesh@e.email Eg)
Main account: Account {name=prateesh@e.email, type=e.foundation.webdav.eelo}
URL: https://ecloud.global/remote.php/dav/addressbooks/users/prateesh@e.email/contacts/
Sync automatically: true
SQLITE DUMP
android_metadata
| locale |
| en_GB |
----------
services
| _id | accountName | authState | accountType | addressBookAccountType | service | principal |
| 1 | prateesh@e.email | <null> | e.foundation.webdav.eelo | foundation.e.accountmanager.eelo.address_book | carddav | https://ecloud.global/remote.php/dav/principals/users/prateesh@e.email/ |
| 2 | prateesh@e.email | <null> | e.foundation.webdav.eelo | foundation.e.accountmanager.eelo.address_book | caldav | https://ecloud.global/remote.php/dav/principals/users/prateesh@e.email/ |
----------
sqlite_sequence
| name | seq |
| services | 2 |
| homesets | 2 |
| collections | 2 |
----------
homesets
| _id | serviceID | url |
| 1 | 1 | https://ecloud.global/remote.php/dav/addressbooks/users/prateesh@e.email/ |
| 2 | 2 | https://ecloud.global/remote.php/dav/calendars/prateesh@e.email/ |
----------
collections
| _id | serviceID | type | url | privWriteContent | privUnbind | forceReadOnly | displayName | description | color | timezone | supportsVEVENT | supportsVTODO | source | sync |
| 1 | 1 | ADDRESS_BOOK | https://ecloud.global/remote.php/dav/addressbooks/users/prateesh@e.email/contacts/ | 1 | 1 | 0 | Contacts | <null> | <null> | <null> | 0 | 0 | <null> | 1 |
| 2 | 2 | CALENDAR | https://ecloud.global/remote.php/dav/calendars/prateesh@e.email/personal/ | 1 | 1 | 0 | Personal | <null> | <null> | <null> | 1 | 1 | <null> | 1 |
----------
SYSTEM INFORMATION
Android version: 8.1.0 (lineage_whyred-userdebug 8.1.0 OPM7.181205.001 f8b793439d dev-keys)
Device: Xiaomi Redmi Note 5 Pro (whyred)
--- END DEBUG INFO ---
```Jalon-JabugoPrateesh Prateesh https://gitlab.e.foundation/e/backlog/-/issues/587Google mention in Google Video Player2020-04-27T19:09:03ZAnonymeGoogle mention in Google Video PlayerHi,
when the prompt in order to choose the video player we want pops up, there is the word Google.
A similar issue (e/management#94) has been raised one year ago and closed because "The issue has been fixed".
![IMG_20191116_133934](/u...Hi,
when the prompt in order to choose the video player we want pops up, there is the word Google.
A similar issue (e/management#94) has been raised one year ago and closed because "The issue has been fixed".
![IMG_20191116_133934](/uploads/391cd6c074d1001b6438292f5000b556/IMG_20191116_133934.jpg)Jalon-JabugoRomain HunaultRomain Hunaulthttps://gitlab.e.foundation/e/backlog/-/issues/712Telegram will not install2020-04-27T19:07:24ZDale ScheetzTelegram will not installJalon-Jabugohttps://gitlab.e.foundation/e/backlog/-/issues/1016"this app is currently unavailable" message in Apps store2020-04-27T19:07:24ZRik Viergever"this app is currently unavailable" message in Apps storesee attached picture![image](/uploads/cbea23056df88f09a4c68c819bc2268f/image.png)see attached picture![image](/uploads/cbea23056df88f09a4c68c819bc2268f/image.png)Jalon-JabugoNivesh Krishnanivesh@e.emailNivesh Krishnanivesh@e.emailhttps://gitlab.e.foundation/e/backlog/-/issues/1032Disable Forward lookup2020-04-27T17:25:23ZRomain HunaultDisable Forward lookup## Summary
<Summarize the improvement briefly and precisely>
**This improvement concerns** <Tick at least one of the following choices>
- [ ] UI
- [ ] Behavior
- [x] Privacy
## Description
**What is the current behavior?**
<What act...## Summary
<Summarize the improvement briefly and precisely>
**This improvement concerns** <Tick at least one of the following choices>
- [ ] UI
- [ ] Behavior
- [x] Privacy
## Description
**What is the current behavior?**
<What actually happens>
The **forward lookup** setting is enabled by default in the Dialer
**What is the improved behavior?**
<What you should see instead>
The **forward lookup** setting is disabled by default
**What does it bring?**
Privacy (don't send data to a third party by default)
<Why this improvement is needed>
## Examples
<Give the example of what users will be able to accomplish with the improvement>
## Validation
<List test case that will be run to validate that the issue is working as expected>
Install /e/ and check that **forward lookup** is disabled by default, inside Dialer Settings.
Ideally, it should also be disabled after an update.
FYI @arnauvp @gaelJalon-JabugoMohit MaliMohit Malihttps://gitlab.e.foundation/e/backlog/-/issues/1041Tasks sync issues2020-04-14T17:56:04ZRomain HunaultTasks sync issues- /e/ version: /e/ test hobart
- Device model: kiwi (nougat)
- When it started to occur: both on fresh install and after update
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: -
## Summary
<Summarize the bug ...- /e/ version: /e/ test hobart
- Device model: kiwi (nougat)
- When it started to occur: both on fresh install and after update
- Reproducible with the last /e/ version: -
- Reproducible with LineageOS: -
## Summary
<Summarize the bug encountered briefly and precisely>
On the last AccountManager version, it seems the Tasks app synchronisation is broken.
<Please tick one of the following sentences if relevant>
- [ ] The device is unusable
- [ ] The bug is the source of a data loss or a big waste of time
- [ ] The bug concerns a third party app
- [ ] The bug concerns security
- [ ] The bug concerns privacy
## The problem
**Steps to reproduce**
<How one can reproduce the issue>
1. Install the /e/ test build
1. Add an /e/ account
1. Add a new task in Tasks app
**What is the current behavior?**
<What actually happens>
1. The task is not synced on ecloud
1. A white page is shown on a regular basis (only on install after update)
**What is the expected correct behavior?**
<What you should see instead>
Tasks have to be synced without any configuration, both when the update is installed on a fresh installation or after updating a previous version.
## Technical informations
> The Tasks app used is **OpenTasks**, and not the fork we did.
**Relevant logs (`adb logcat`)**
<Paste any relevant logs in the codeblock bellow>
The following log appears when the white page appears.
```
2020-03-09 10:51:44.113 3486-3506/foundation.e.accountmanager E/davx5: [foundation.e.accountmanager.App] Unhandled exception!
EXCEPTION java.lang.IllegalStateException: Migration didn't properly handle: service(foundation.e.accountmanager.model.Service).
Expected:
TableInfo{name='service', columns={principal=Column{name='principal', type='TEXT', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='null'}, authState=Column{name='authState', type='TEXT', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='null'}, accountName=Column{name='accountName', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}, id=Column{name='id', type='INTEGER', affinity='3', notNull=true, primaryKeyPosition=1, defaultValue='null'}, accountType=Column{name='accountType', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}, type=Column{name='type', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}, addressBookAccountType=Column{name='addressBookAccountType', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}}, foreignKeys=[], indices=[Index{name='index_service_accountName_type', unique=true, columns=[accountName, type]}]}
Found:
TableInfo{name='service', columns={principal=Column{name='principal', type='TEXT', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='NULL'}, authState=Column{name='authState', type='TEXT', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='null'}, accountName=Column{name='accountName', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}, id=Column{name='id', type='INTEGER', affinity='3', notNull=true, primaryKeyPosition=1, defaultValue='null'}, accountType=Column{name='accountType', type='TEXT', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='null'}, type=Column{name='type', type='TEXT', affinity='2', notNull=true, primaryKeyPosition=0, defaultValue='null'}, addressBookAccountType=Column{name='addressBookAccountType', type='TEXT', affinity='2', notNull=false, primaryKeyPosition=0, defaultValue='null'}}, foreignKeys=[], indices=[Index{name='index_service_accountName_type', unique=true, columns=[accountName, type]}]}
at androidx.room.RoomOpenHelper.onUpgrade(RoomOpenHelper.java:103)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.onUpgrade(FrameworkSQLiteOpenHelper.java:124)
at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:256)
at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:163)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper$OpenHelper.getWritableSupportDatabase(FrameworkSQLiteOpenHelper.java:92)
at androidx.sqlite.db.framework.FrameworkSQLiteOpenHelper.getWritableDatabase(FrameworkSQLiteOpenHelper.java:53)
at androidx.room.RoomDatabase.inTransaction(RoomDatabase.java:476)
at androidx.room.RoomDatabase.assertNotSuspendingTransaction(RoomDatabase.java:281)
at foundation.e.acc
2020-03-09 10:51:44.113 3486-3506/foundation.e.accountmanager E/davx5: ountmanager.model.ServiceDao_Impl.getByType(ServiceDao_Impl.java:293)
at foundation.e.accountmanager.PackageChangedReceiver$Companion.updateTaskSync(PackageChangedReceiver.kt:36)
at foundation.e.accountmanager.App$onCreate$1.invoke(App.kt:85)
at foundation.e.accountmanager.App$onCreate$1.invoke(App.kt:30)
at kotlin.concurrent.ThreadsKt$thread$thread$1.run(Thread.kt:30)
```
**Relevant screenshots**
<Screenshots of the problem>
![screenshot_20200309_11_13_10](/uploads/bd29aad2ee788982f67e01e88b4ad2b6/screenshot_20200309_11_13_10.png)
## Solutions
**Workaround**
<To get the feature working or at least to make the device usable>
**Possible fixes**
<Any idea to fix the issue or a link to the line of code that might be the cause for this problem>Jalon-JabugoRomain HunaultMohit MaliRomain Hunault