



Network Errors

In the current library version (0.4.3), there’s a bug that hides network errors. They become indistinguishable from requests that are taking too long. There’s a pending PR to fix it. But until then, we’re using our own fork.





Context

In the examples given, BlockstackSession is initialized with an Activity Context . But for almost all Blockstack operations, the Application Context . This is useful for taking that logic out of the Activity classes and properly architecture your code.

But the login call redirectUserToSignIn requires a BlockstackSession with an Activity Context . That’s because it opens a WebView from the inside. If you still want to use the Application Context for all the other calls, just make sure the different BlockstackSession instances share the same SessionStore . That way, all BlockstackSession instances read and store the session data from the same location.





APK signing

This one is not directly related with Blockstack, but something to keep an eye on. During login, users first sign in on Blockstack inside a WebView. Then the authentication response comes back to the Android app through an app link. For that process to be seamless, the app link should be automatically verified.

Google Play now encourages delegating the APK signing process to them. But that means that the sha256_cert_fingerprints that ends up in the server assetlinks.json file will not be the one you would expect. Your upload key signing gets removed from the APK. You need to fetch the correct fingerprint from your Google Play Dashboard under Release management > App signing .



