[Passed] Final proposal for continuing developments on Android wallet (v3.0 released)

[woolly_sammoth]

Thanks for finding and reporting this.

You’re welcome. Can I pretend it was done deliberately?

(The android wallet will be statying as it is for the foreseeable future. I’ve already sent some reports to Matthew but am happy to help debugging)

[woolly_sammoth]

Some good news. I have the 320 NuBits in my main wallet now.
I built a python tool using Google ProtoBuf to decode the android wallet export and recover the private keys.
I’ll look at open sourcing that code if there’s an interest as it could be a useful tool if anyone else finds themselves in a similar situation.

I’m happy to leave the android wallet in its current state for as long as neccessary now.

[mhps]

decode the android wallet export and recover the private keys

Was the key encrypted?

[woolly_sammoth]

the wallet export was encrypted with a passphrase but I knew that as it was mine.
Once the wallet file is decrypted, the keys are held in the Protobuf format. That mesans you can;t just open the file and read them, they need extracting in a certian way and then converting from bytes to base58check encoded WiF keys.

Luckily the offending address was generated using the old android wallet. If it had been generated using the ne HD wallet method, it would have been a bit more work.

[tylergillies]

Does this version have shapeshift? I thought was going to be in the 2.0 version? Or was that 3.0?

[Cybnate]

@woolly_sammoth. Good to hear that you managed to get your funds back. With that you proofed it can be done, and it is not just a statement, although it is not a simple exercise. I suspect I wouldn’t have been able to do alone what you did. Thanks for your time and showing the way to us all.

Anyway, I understand that Matthew has been in contact with you for more logs in an attempt to obtain more information.

Update to 2.02

He left me with another update which fixes a bug he found while tracing things down. I’ve uploaded this version as v2.02 here. I’ve also updated the link in the first release post.

Does this version have shapeshift? I thought was going to be in the 2.0 version? Or was that 3.0?

Version 3.0 (release 2 of the grant) will have shapeshift. The development of that has just started. The target date for this release, which will be brand new code, is before 15 June. The Shapeshift part that is. I bet we are all looking forward to that.

[woolly_sammoth]

I have been in contact with Matthew who has been very helpful. Unfortunately, none of the updates so far have fixed the stalled blockchain.
It would be good for the wallet to handle Custodial Grants but I don’t want too much effort to be put into this bug if it slows down development on the Shapeshift integration. I think it’s enough of an edge case, and we now have a work around should it happen again.

[GLock]

No issues so far on Android 4.4.4 with ver 2.01 and 2.02

[GLock]

After playing a bit with the app I have noticed that every time I tap on Settings -> Data usage i get a message “Unfortunately, Settings has stopped” and I can’t access Data usage.
Is anyone else experiencing the same?

[woolly_sammoth]

It works for me. It takes me through to the standard android data usage page where I can set data limits, turn mobile data on / off and see which apps have been using the most data.
I wonder if your data usage page is in an unexpected place?

[GLock]

Could be, the app is installed on a Xiaomi Mi 3, with MIUI interface.

[Cybnate]

Haven’t seen that behaviour on my device either. Explicitly tested a few scenarios, but it just works.

[GLock]

Testing also on Sony Xperia Z with Android 4.4.2 and Samsung Tablet with 4.0.4
No problems so far, and I don’t have the Data usage issue that I am experiencing with the Xiaomi MIUI

[Cybnate]

We have arrived at the end of our 1 week testing period. It looks like the Android client is stable. Only a report from Glock on a somewhat non-standard device I believe and the issue Woolly reported about the blockchain stalling at an custodial address it owns. Although I like to see them fixed, I don’t think they are contractual showstoppers for the final payment of release 1.

I therefore propose to pay the Developer on invoicing for release 1 and with that the APK will be published on Google Play. Please let me know if you don’t agree or forgot to submit issues you found.

[Sebsebzen]

NuBits wallet working fine on Google Nexus 5.

[woolly_sammoth]

Matthew sent me an updated wallet apk yesterday that fixed the Custodial Grant issue.
I’d like to thank him for the hard work he put into this fairly edge case issue.

[Cybnate]

NuBits wallet working fine on Google Nexus 5.

Thanks for testing. What version are you using Kitkat or Lollipop?

Matthew sent me an updated wallet apk yesterday that fixed the Custodial Grant issue. I’d like to thank him for the hard work he put into this fairly edge case issue.

It is great that he did fix it. I won’t hesitate to pay the invoice as he went the extra mile here. So from now on you can even receive and make use of your custodial grant when on the road or while waiting at the airport!
And thanks to Woolly we know we can retrieve the keys from the Android wallet assuming you know the passphrase.

NuBits Android wallet v2.0 download link
You can now download or update the official 2.0 update from Google Play here
When you already had 1.0 installed through Google Play you already received an update or it is waiting for you depending on your settings. Enjoy!

[tomjoad]

I’ve updated the download link on nubits.com/download and tweeted it out too. I’m not completely satisfied with the layout and spacing of the Download page right now, so I’ll try and make time to improve it soon.

[Sebsebzen]

@cybnate NuBits Wallet 2.01 running on Android Lollipop. Will update to newer version and try too.

[Sebsebzen]

@cybnate Uninstalled and re-installed new version from Google Play. Works fine. However, one issue: When importing wallet back-up, notification pops-up that app doesn’t respond and asks me if I want to wait or terminate process. I pressed wait and after few seconds import was completed. Could be confusing to some users.