Android M

Question

Android M

SlayerOrnstein opened this issue 10 years ago · 7 comments

secrecy stuck at adding to vault on Android M

Answer 1 · 2015-06-24T19:16:00.000Z

I managed to create a debug log via android studio
http://pastebin.com/y0NXsWtc

Answer 2 · 2015-06-24T20:34:54.000Z

Line 57-58 state that protobuf cannot deserialize the vault header. Either your vault header is broken and this can be 'fixed' by creating a new vault, or the storage layer in Android M has changed again and Secrecy just can't access that file. The storage layer will be rebuild, but I honestly don't think that will happen too soon.

Answer 3 · 2015-06-24T21:06:14.000Z

This happened when creating a vault so it's probably the storage layer changes in Android M

Answer 4 · 2015-06-24T21:10:43.000Z

I guess in that case we can only start to adapt to these changes when the API is stable and documented.

Answer 5 · 2015-06-24T21:17:55.000Z

Have you used secrecy before updating to Android M? Otherwise it would be interesting if the SECRECYFILES folder is created, because nothing in the log files shows signs of an error. Which could mean that the folder is already created, or an error when creating that folder is not logged.

Answer 6 · 2015-06-24T23:55:35.000Z

Yes but it was a clean install of Android M but the SECRECYFILES folder is still created after opening the app for the first time

Answer 7 · 2015-08-17T19:44:43.000Z

Hey guys just a heads up secrecy seems to be working normally again I'm preview 3