MirakelX / mirakel-android

Easy task management for professionals
http://mirakel.azapps.de/
384 stars 117 forks source link

Import of taskd-config fails/adding Taskwarrior Sync impossible #156

Closed defkev closed 10 years ago

defkev commented 10 years ago

No error message returned, the dialog just closes and that's it.

Regardless of wherever i add the Account within Mirakel > Settings > Sync or Settings > Accounts > Add Account > Mirakel

Reproducible using taskd running in my own lab as well as your azapps.de.

A tcpdump on my taskd server shows zero incoming connections will adding the account, thus i suspect something fails during import of the config.

Synchronization using Taskwarrior (2.3.0.beta2) works on my lab and your server as expected.

Android 4.4 KitKat Stock taskd 1.0.0.beta2 on Ubuntu 12.04.3 LTS

Cheers

weiznich commented 10 years ago

I've tested the sync to azapps.de again, with a newly created taskdconfig. There was no problem to import the config.

Is aaccount created? If so there should be no problem with the import. Can you try to make some logs during the sync using logcat? Looking for the Tags TLSClient and TaskWarroirSync.

Which version of mirakel do you use? Due to taskd-api-changes there was a change in the configfiles. So the current configfiles will only work with Mirakel 2.1 and above.

defkev commented 10 years ago

Mirakel is 2.1.2 from the Play Store.

I did a duplicated setup under CentOS 6.4 and recompiled taskd/Taskwarrior from scratch.

Behavior stays the same, Taskwarrior works/Mirakle doesn't.

I'll get back to you with a logcat.

Thanks so far.

yvesago commented 10 years ago

certainly fix in developing branch, see issue #127 ... wait for next release

itadventurer commented 10 years ago

That's right, we will publish the version with the bugfix today ;)

defkev commented 10 years ago

Awesome

I'll give it a shot once it hits Google Play.

Thanks!

defkev commented 10 years ago

Nope, still doesn't work, behavior as it is stays the same in Version 2.1.3 - config import fails w/o any error message.

Except for one thing:

Version 2.1.2 said something like "Exporting Database to /storage/emulated/whatever...db" on first start/after a Clear data.

Version 2.1.3 says "There was an error will exporting the database."

logcat *:E -v long shows

E/de.azapps.mirakel.model.DatabaseHelper( 4403): Upgrading database from version 7 to 25 E/mypck ( 4403): /data/data/null/databases/mirakel.db: open failed: ENOENT (No such file or directory) E/mypck ( 4403): java.io.FileNotFoundException: /data/data/null/databases/mirakel.db: open failed: ENOENT (No such file or directory) E/mypck ( 4403): at libcore.io.IoBridge.open(IoBridge.java:409) E/mypck ( 4403): at java.io.FileInputStream.(FileInputStream.java:78) E/mypck ( 4403): at de.azapps.tools.FileUtils.copyFile(FileUtils.java:75) E/mypck ( 4403): at de.azapps.mirakel.helper.export_import.ExportImport.exportDB(ExportImport.java:83) E/mypck ( 4403): at de.azapps.mirakel.model.DatabaseHelper.onUpgrade(DatabaseHelper.java:101) E/mypck ( 4403): at de.azapps.mirakel.model.DatabaseHelper.onCreate(DatabaseHelper.java:86) E/mypck ( 4403): at android.database.sqlite.SQLiteOpenHelper.getDatabaseLocked(SQLiteOpenHelper.java:252) E/mypck ( 4403): at android.database.sqlite.SQLiteOpenHelper.getWritableDatabase(SQLiteOpenHelper.java:164) E/mypck ( 4403): at de.azapps.mirakel.model.MirakelContentProvider.onCreate(MirakelContentProvider.java:289) E/mypck ( 4403): at android.content.ContentProvider.attachInfo(ContentProvider.java:1589) E/mypck ( 4403): at android.content.ContentProvider.attachInfo(ContentProvider.java:1560) E/mypck ( 4403): at android.app.ActivityThread.installProvider(ActivityThread.java:4771) E/mypck ( 4403): at android.app.ActivityThread.installContentProviders(ActivityThread.java:4366) E/mypck ( 4403): at android.app.ActivityThread.handleBindApplication(ActivityThread.java:4306) E/mypck ( 4403): at android.app.ActivityThread.access$1400(ActivityThread.java:135) E/mypck ( 4403): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1457) E/mypck ( 4403): at android.os.Handler.dispatchMessage(Handler.java:102) E/mypck ( 4403): at android.os.Looper.loop(Looper.java:137) E/mypck ( 4403): at android.app.ActivityThread.main(ActivityThread.java:4998) E/mypck ( 4403): at java.lang.reflect.Method.invokeNative(Native Method) E/mypck ( 4403): at java.lang.reflect.Method.invoke(Method.java:515) E/mypck ( 4403): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:777) E/mypck ( 4403): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:593) E/mypck ( 4403): at dalvik.system.NativeStart.main(Native Method) E/mypck ( 4403): Caused by: libcore.io.ErrnoException: open failed: ENOENT (No such file or directory) E/mypck ( 4403): at libcore.io.Posix.open(Native Method) E/mypck ( 4403): at libcore.io.BlockGuardOs.open(BlockGuardOs.java:110) E/mypck ( 4403): at libcore.io.IoBridge.open(IoBridge.java:393) E/mypck ( 4403): ... 23 more

sdcard has a folder called mirakel with multiple mirakel%date%%time%.db files (one for every time i started the app i suppose) in it.

I suspect that the import would work this time if the initial database export wouldn't fail now...

Wan't me to fill a new bug report or should we stay in here?

weiznich commented 10 years ago

It's ok to stay here, due to this issue should be fixed with 54786cb93d

px4n commented 10 years ago

I'm also experiencing a similar issue, has this been released yet? Thanks!

weiznich commented 10 years ago

The fix for the first issue is already released. The second part not, but the app should start also with this crash(It's only about that it faild to backup the current database befor upgrading it.) We will release this fix as soon as posible.

defkev commented 10 years ago

Just installed 2.1.4 from Google Play.

First things first, the Database Export error message is gone...hurray.

Unfortunately, the taskdconfig import and with this adding a Mirakle Account for Taskwarrior sync still doesn't work.

The behavior is still exactly the same as of my initial report thous i am going to spare us all repeating myself.

Yet, i have done another logcat-run using:

adb logcat *:D -v long > mirakel_taskwarrior.txt

which shows no errors will importing the configuration file and tapping Sign in.

This is the only thing i could dig up which is definitly somewhat related to Mirakel i suppose:

I/ActivityManager(  739): START u0 {act=android.settings.ADD_ACCOUNT_SETTINGS cmp=com.android.settings/.accounts.AddAccountSettings} from pid 18979
I/ActivityManager(  739): START u0 {cmp=com.android.settings/.accounts.ChooseAccountActivity} from pid 18979
I/ActivityManager(  739): Displayed com.android.settings/.accounts.ChooseAccountActivity: +141ms (total +147ms)
I/ActivityManager(  739): START u0 {cmp=de.azapps.mirakelandroid/de.azapps.mirakel.sync.AuthenticatorActivity (has extras)} from pid 18979
I/WindowManager(  739): Screenshot max retries 4 of Token{427e0398 ActivityRecord{42ba2518 u0 com.android.settings/.accounts.AddAccountSettings t342}} appWin=Window{4289ccf8 u0 com.android.settings/com.android.settings.accounts.AddAccountSettings} drawState=1
W/WindowManager(  739): Screenshot failure taking screenshot for (1080x1920) to layer 21020
I/ActivityManager(  739): Displayed de.azapps.mirakelandroid/de.azapps.mirakel.sync.AuthenticatorActivity: +76ms
I/ActivityManager(  739): START u0 {act=android.intent.action.CHOOSER cmp=android/com.android.internal.app.ChooserActivity (has extras)} from pid 19388
W/IntentResolver(  739): resolveIntent: multiple matches, only some with CATEGORY_DEFAULT
W/IntentResolver(  739): resolveIntent: multiple matches, only some with CATEGORY_DEFAULT
I/ActivityManager(  739): START u0 {act=android.intent.action.GET_CONTENT cat=[android.intent.category.OPENABLE] typ=*/* flg=0x3000000 cmp=com.android.documentsui/.DocumentsActivity} from pid 19388
W/IntentResolver(  739): resolveIntent: multiple matches, only some with CATEGORY_DEFAULT
D/Documents(21173): Current stack: 
D/Documents(21173):  * Root{authority=com.android.externalstorage.documents, rootId=primary, title=Internal storage}
D/Documents(21173):  +-- Document{docId=primary:Download, name=Download}
D/Documents(21173):  +-- Document{docId=primary:, name=0}
I/ActivityManager(  739): Displayed com.android.documentsui/.DocumentsActivity: +186ms (total +226ms)
D/Documents(21173): userMode=0, userSortOrder=0 --> mode=1, sortOrder=1
D/Documents(21173): onFinished() [content://com.android.externalstorage.documents/document/primary%3ADownload%2Ftaskdconfig.html]

Hell, i don't even wanna know why it's trying to take a screenshot so no questions asked...

The taskdconfig.html is the config downloaded from your server at azapps.de

As i initially state this is a Nexus 5 running KitKat 4.4 untouched Stock

Just for the sake of it i tried the exact same procedure on a Galaxy Nexus (Samsung GNex) running MIUI V5 Android 4.2 rooted, where everything is working absolutely fine.

So looks to me this entire problem is somewhat related to Android 4.4

Thanks for the efforts so far Cheers

itadventurer commented 10 years ago

It is not your fault. We just used the beta branch to update the app and the fix was on another branch. We will publish today a beta app with this changes inside. If you install it this auld be fixed. (If you don't want to use Google+ i can also publish the apk on github.) I'm afraid that there are some new bugs so I don't want to publish an unstable app ;)

defkev commented 10 years ago

Link to your Community Page?

itadventurer commented 10 years ago

https://plus.google.com/communities/110640831388790835840

defkev commented 10 years ago

Just tried the latest Beta from Google Play from 21. November, yet it still says 2.1.4 in the Change log, but the Problem persists.

Hell, it's almost like the config selection isn't accepting any file i feed it, no matter what it's a taskd-config or an image for example, the result is always the same after tapping Sign in:

No error message -> No account added -> The dialog just closes.

itadventurer commented 10 years ago

Oh no, I don't know what's up. I'm away this weekend and will look on Monday on this. Sorry...

weiznich commented 10 years ago

Can you send use(mirakel@azapps.de) such a taskdconfig-file for testing? So we can take again a look at this?

defkev commented 10 years ago

Well, you can get one from your very own server as this is what i used for testing.

  1. Log in to http://mirakel.azapps.de/taskdconfig
  2. Download the http://mirakel.azapps.de/taskdconfig generated taskd-config

The exact same configuration file which is working in Android 4.2 isn't working in 4.4

Regardless if i am using your server and certificates or my own.

Taskwarrior 2.3.0 Beta 2 is also working flawlessly with these configuration files.

btw. thanks for reopening the ticket, as i really start to feel dumb for repeating myself.

yvesago commented 10 years ago

I made some tests with my server :

maybe problems come with a big tx.data file on taskd server. This file could be removed and re-create with a "task sync initialize" on the mais taskwarrior client.

weiznich commented 10 years ago

OK I've created a new Account on our server to test again. The file is imported without errors, an account is created. At the time I run a early alpha-build of CM11(also kitkat), so this problem should not be related to the android-version.

Can you take a look into the *.taskdconfig-file? The structure must be as follow: username: ---your username here-- org: --your org here-- user key: --your key here--- server: azapps.de:6544 Client.cert: -----BEGIN CERTIFICATE----- ---some text here--- -----END CERTIFICATE----- Client.key: -----BEGIN RSA PRIVATE KEY----- --some text here-- -----END CERTIFICATE----- ca.cert: -----BEGIN CERTIFICATE----- MIIDtTCCAp+gAwIBAgIEUngOqjALBgkqhkiG9w0BAQUwfTELMAkGA1UEBhMCU0Ux HjAcBgNVBAoMFUfDtnRlYm9yZyBCaXQgRmFjdG9yeTESMBAGA1UEBwwJR8O2dGVi b3JnMRowGAYDVQQIDBFWw6RzdHJhIEfDtnRhbGFuZDEeMBwGA1UEAwwVR8O2dGVi b3JnIEJpdCBGYWN0b3J5MB4XDTEzMTEwNDIxMTYyNloXDTE0MTEwNDIxMTYyNlow fTELMAkGA1UEBhMCU0UxHjAcBgNVBAoMFUfDtnRlYm9yZyBCaXQgRmFjdG9yeTES MBAGA1UEBwwJR8O2dGVib3JnMRowGAYDVQQIDBFWw6RzdHJhIEfDtnRhbGFuZDEe MBwGA1UEAwwVR8O2dGVib3JnIEJpdCBGYWN0b3J5MIIBIDALBgkqhkiG9w0BAQED ggEPADCCAQoCggEBAMfpRi88/pEw9ofFPMdLy9/Ev8JZebbK9dd71Sbxkrn1DGg5 JU/SgoUpp+dY+CgDrZPg2j2m2oh2QUke1GOpW/gpwy5nzEUsZF5Jww+/AXE2bxtr TzmdxGiKsXcbX2bn9Or7YSJIn9sW489Uj/4odVC3G2LksBMTW+anpNipYP6GbD3i vEpt+WWPEfVlQkHl9cgZI8zYyxEozJnNTjp07K4zR0inSgsPSH5jfz15UOlwoOWI k3q1CNvoWHJcctcCkr94uf26uwmkX2dtsl8A9RM4MlrwTmAhG47/DPk4xF48fFPM MoehAbGCsvZrHb7rPVC5RUw6tf64TqR4tsSO/N8CAwEAAaNDMEEwDwYDVR0TAQH/ BAUwAwEB/zAPBgNVHQ8BAf8EBQMDBwQAMB0GA1UdDgQWBBTrXwIcrZxC/B2Szj1c pz+gwdp3ojALBgkqhkiG9w0BAQUDggEBAAuZ/OrQim+r7LsovoIIuD9vFjNuh4fD 0Nelto+HBXL6LmnrkyEQxToyDlH6deKPjqSg/3bif84BwjyWrkMHZNhOR4n5e3HZ pCg9oIVRmP6MoKc8k5he3G9AnVs0tRmgL+OIwaA26P2mK9h9ghmh+e+DXwweC56B WyY6KuRyV4fKi3Rt0NAwBXxIJ58YNgcbyOUqU21Q+zkVA6ySDDEehcVV3Ug4a99c +mQqwUlhyxcsqAEwkfE88hMMJpKfCk89YId0CNYPWxuaHNfN6hXbyjVL4g3Pinhh aEA/4GkjPIvcvOYktqJxf8OjDCIXCAkMsTXD51185pfTw1rHKB5b1tM= -----END CERTIFICATE-----

If the file is structured as shown above, please check again if you really selected this file.

@yvesago : We will restructure the account-interface in Mirakel 2.2 to support more than one account at the same time, so we will change this there

defkev commented 10 years ago

I just reinstalled Mirakel Beta, which now indeed says Beta, and created another account on your server using a disposable mail address so feel free to mess around with the below config.

Despite that the structure of the configuration file looks exactly like what it looked before the account creation still doesn't work on my Nexus 5...

username: mirakelnotworking
org: Public
user key: f6734b1e-da57-40af-9b21-e0a694866f9e
server: azapps.de:6544
Client.cert:
-----BEGIN CERTIFICATE-----
MIIDqzCCApWgAwIBAgIEUo/gbzALBgkqhkiG9w0BAQUwfTELMAkGA1UEBhMCU0Ux HjAcBgNVBAoMFUfDtnRlYm9yZyBCaXQgRmFjdG9yeTESMBAGA1UEBwwJR8O2dGVi b3JnMRowGAYDVQQIDBFWw6RzdHJhIEfDtnRhbGFuZDEeMBwGA1UEAwwVR8O2dGVi b3JnIEJpdCBGYWN0b3J5MB4XDTEzMTEyMjIyNTMzNVoXDTE0MTEyMjIyNTMzNVow QDEeMBwGA1UECgwVR8O2dGVib3JnIEJpdCBGYWN0b3J5MR4wHAYDVQQDDBVHw7Z0 ZWJvcmcgQml0IEZhY3RvcnkwggEgMAsGCSqGSIb3DQEBAQOCAQ8AMIIBCgKCAQEA oCdu/MbnagSd/vbUutM9jlNTHvwPxutpT3Cp0u0t5ZjZl51l9cHZzmJEjqIuSGj6 JfUyq5isu1vJca+K7Vb+JidxMXnMKXjjBOFZ86KQiZxzxMgEaNP7MHvUzD2LExl6 nk6UwzcJhmmfeC/IM0QqdpPve1HDEViqXbLcDiRSk12op8/E2yk2/nSvl/H1tUCn 5FWAPG9E9WIWF6RzxGEBUFw8PqrY1fC2I/+y3ma+kDPAMuiejyum7hEknXYvZ+Gm kN+KIfVsF/WYiuQxifhU9E0/zaxMXzkK9PsJ9Bd5xVUzo+li4Nc2I7Ksx6LewTID qBDrfTs4uhxGG4wifoqr/wIDAQABo3YwdDAMBgNVHRMBAf8EAjAAMBMGA1UdJQQM MAoGCCsGAQUFBwMCMA8GA1UdDwEB/wQFAwMHoAAwHQYDVR0OBBYEFGAz9LPGpMsi H4f+qpDxGqyTJ1FCMB8GA1UdIwQYMBaAFOtfAhytnEL8HZLOPVynP6DB2neiMAsG CSqGSIb3DQEBBQOCAQEADtvkPtiD/vLbgdCykREFZV+dI5xaAj2iDndwDbBLM6Cz DL+Pz58UxewpHVDPjwn8ywgFqpnesblpc+uLrX46kwgRZB3tWNSV2r2hKW3pzAMe ox9STCxb2+yGHz1vSiFyx0aqvJ9sGlAXBGQ4dfE76sYr/gzev9EcNa6GDNVYSgFI 6jicGPMCQ3Yug2u4w1S2FbmFMbikDV39o0P9bmwt2Y5sEm7K1RQPlTPKZMSxbCL+ amxjy5iDVNa7iG6Fv3qwFUxGqgmidJXGPOT8GHzfHn9KSb96KwnB/INxhX29C66j Df9C/AnxkyTEVFgHUh0Iu1c8i6dN+iPOytjDMNG4dA==
-----END CERTIFICATE-----
Client.key:
-----BEGIN RSA PRIVATE KEY-----
MIIEpAIBAAKCAQEAoCdu/MbnagSd/vbUutM9jlNTHvwPxutpT3Cp0u0t5ZjZl51l 9cHZzmJEjqIuSGj6JfUyq5isu1vJca+K7Vb+JidxMXnMKXjjBOFZ86KQiZxzxMgE aNP7MHvUzD2LExl6nk6UwzcJhmmfeC/IM0QqdpPve1HDEViqXbLcDiRSk12op8/E 2yk2/nSvl/H1tUCn5FWAPG9E9WIWF6RzxGEBUFw8PqrY1fC2I/+y3ma+kDPAMuie jyum7hEknXYvZ+GmkN+KIfVsF/WYiuQxifhU9E0/zaxMXzkK9PsJ9Bd5xVUzo+li 4Nc2I7Ksx6LewTIDqBDrfTs4uhxGG4wifoqr/wIDAQABAoIBADjuu8BFbyebm5Tz Jx2BEZ1iVqapoWwr7KRuXxiZ8xpvE08YB5JtRqHdAhUYZ06bbu2GdGxW2nTCROLS rhcAOVnT5KPbce3+SOnHuIPpMuuQgAEgv5yKWv3Zz4SJjkKMaLAVLEIXcx3it2tw xQEght3fah9TKf6lH+8uMZcfZ3F2Jo9o3kZY93F+nxVf7ipz2iIV67tIzuVLNVI3 QjrnG9pOhZDo5lSoxnLevaG31BSF3yxfpEWp2S+01zFiNIVbbYXGlDKr8ULahpL+ X1lJATh4+m8b5JzXnV5NzucpYEjdYXSLkZ3Zvaen6CF1O8/L+A1HtcGlesNSpEyq Imnh6UUCgYEAx2yWyPaSicwJKC4DYzGLMBslgwVb700Xy2MnVcxTawkvxcHMJZ3q uZ4L0Gr9XDz/CXQH8Ue091QHG+B1wLy4yzawvpXk7z2dctDnnJ4RyDcczXHPSsWM iwMmvMVhKZOJAOwWEh7HsEyC8N6m7YUtpLJcBa6teo4jB9qoSeAoG+sCgYEAzZbO Ll2F8CvMgshCx96WYY0+5CpAcfIWJUNin/bc1EDDbVMEDsMB/bEhDrZQezcU9gN5 Yp2jWBRLdahKNA0BaQARDNCdB2J7ExFy2b634eM762ZIOOE+X2i/jw1cDlEmpRL7 8WQ2CtEQt2U4Ko9h2wgPSX0jhRnHLHL1fhX7zz0CgYEAkxLdnXZjmiaU9kIBE429 VgwfPSKdq72Sd9g3cUpQlxbeWZ1UfsWZD62kjt/o3LbLbGBbXzGAIAujdoaysSM9 sfkynkwT2/D4Bm5U8ieNe7hRkJ6Hv2A0B22aiwuSXcRF/R0gJdr3cGjtBNFgELnw cI9t2G771++tnCRBisI7MmMCgYEAqXA5u5LOuZOPeNYN2+ZCcGHVzHxaIs8Pm2R/ GzF87N33ctmxhW0I7goXIaX2jKZn+x3/49vh7MzFKFIr3dw+JkisxLAGSzjKEHwX +QerS1tZXfgtW9uf6UhOYFr1XMNbIz+TL26U77NAoLWmZcVINBnfZ4TgSmllcufI FkOOBk0CgYAjI3mxOmdunfIn0oyQnWoLrD3tuU+NvCNQcwv8ea44yFiz9fkS35l+ TYNVUEW8HTjqJfDXX7c8ICSJW9q08apQzMFB6bv2b9LF4IzPvEr5Fxeo2OnrrdiB jDf6iqwtYFioVroaO6G82Oasiff2LUCpaDmj0/CVWM7aXSJQiLPRCA==
-----END RSA PRIVATE KEY-----
ca.cert:
-----BEGIN CERTIFICATE-----
MIIDtTCCAp+gAwIBAgIEUngOqjALBgkqhkiG9w0BAQUwfTELMAkGA1UEBhMCU0Ux HjAcBgNVBAoMFUfDtnRlYm9yZyBCaXQgRmFjdG9yeTESMBAGA1UEBwwJR8O2dGVi b3JnMRowGAYDVQQIDBFWw6RzdHJhIEfDtnRhbGFuZDEeMBwGA1UEAwwVR8O2dGVi b3JnIEJpdCBGYWN0b3J5MB4XDTEzMTEwNDIxMTYyNloXDTE0MTEwNDIxMTYyNlow fTELMAkGA1UEBhMCU0UxHjAcBgNVBAoMFUfDtnRlYm9yZyBCaXQgRmFjdG9yeTES MBAGA1UEBwwJR8O2dGVib3JnMRowGAYDVQQIDBFWw6RzdHJhIEfDtnRhbGFuZDEe MBwGA1UEAwwVR8O2dGVib3JnIEJpdCBGYWN0b3J5MIIBIDALBgkqhkiG9w0BAQED ggEPADCCAQoCggEBAMfpRi88/pEw9ofFPMdLy9/Ev8JZebbK9dd71Sbxkrn1DGg5 JU/SgoUpp+dY+CgDrZPg2j2m2oh2QUke1GOpW/gpwy5nzEUsZF5Jww+/AXE2bxtr TzmdxGiKsXcbX2bn9Or7YSJIn9sW489Uj/4odVC3G2LksBMTW+anpNipYP6GbD3i vEpt+WWPEfVlQkHl9cgZI8zYyxEozJnNTjp07K4zR0inSgsPSH5jfz15UOlwoOWI k3q1CNvoWHJcctcCkr94uf26uwmkX2dtsl8A9RM4MlrwTmAhG47/DPk4xF48fFPM MoehAbGCsvZrHb7rPVC5RUw6tf64TqR4tsSO/N8CAwEAAaNDMEEwDwYDVR0TAQH/ BAUwAwEB/zAPBgNVHQ8BAf8EBQMDBwQAMB0GA1UdDgQWBBTrXwIcrZxC/B2Szj1c pz+gwdp3ojALBgkqhkiG9w0BAQUDggEBAAuZ/OrQim+r7LsovoIIuD9vFjNuh4fD 0Nelto+HBXL6LmnrkyEQxToyDlH6deKPjqSg/3bif84BwjyWrkMHZNhOR4n5e3HZ pCg9oIVRmP6MoKc8k5he3G9AnVs0tRmgL+OIwaA26P2mK9h9ghmh+e+DXwweC56B WyY6KuRyV4fKi3Rt0NAwBXxIJ58YNgcbyOUqU21Q+zkVA6ySDDEehcVV3Ug4a99c +mQqwUlhyxcsqAEwkfE88hMMJpKfCk89YId0CNYPWxuaHNfN6hXbyjVL4g3Pinhh aEA/4GkjPIvcvOYktqJxf8OjDCIXCAkMsTXD51185pfTw1rHKB5b1tM=
-----END CERTIFICATE----- 

@weiznich Interesting comment! CM11 is using Android 4.4 Build KRT16S from Android Open Source will the Nexus 5 is "still" running Build KRT16M and hasn't received an OTA-Update yet.

Furthermore i am aware of some other "Account related" problems which exist on the Nexus 5 but e.g. don't exist on the Nexus 7 running KitKat and those Build KRT16S so maybe all this is tied to the Buildversion i am running and not Mirakel at all?!

Just my 2 cents of course, time will tell.

weiznich commented 10 years ago

Seems really to be a Bug in this android-build. With the posted config I could create a new account.

alphazo commented 10 years ago

I also own a Nexus 5 and cannot import the configuration file generated by http://mirakel.azapps.de

itadventurer commented 10 years ago

Hmm… Thats strange. We will look on this. Maybe it's an issue regarding KitKat?

weiznich commented 10 years ago

I don't thing this is a common kitkat issue, due to it is working for me. It seems to be a android-build related issue. We will need somehow more informations about this to debug it.

defkev commented 10 years ago

Just dropping by for a small update after installing KitKat 4.4.2 Build KOT49H from OTA yesterday.

Mirakel 2.1.4

  1. Behavior unchanged, selecting taskd config for import still yields nothing, no error message, nada.

Mirakel 2.2-beta1+x

  1. Mirakel crashes after selecting either [Scan QR code] or [Select config file] from "Configure Taskwarrior" dialog.
  2. Trying to add a Mirakel account using the systems build in Settings -> Accounts -> Add account just freezes the Settings App.

I submitted at least one crash report from within the beta apk, in hope thinks get sorted out somehow.

Cheers

weiznich commented 10 years ago

I think this should be fixed since 072588bce. If not so please reopen.