Ok so it looks like it's the content resolver method that's not working - and we do have an issue on our side where if the content resolver fails we're not properly falling back to the intent method.

I think maybe it was failing every time for you on 2.0.5 because the content resolver was never used because "remember my choice" option was not selected.

But if you install Amber 2.0.5 from a fresh state and select this option it works.

We'll get a fix out ASAP for the intent fallback - but can you think of something that might have changed with the content resolver logic? 

 How is the event you are sending to the content resolver?
I changed recently to check for id and pubkey 

 Aah ok maybe that's it then - we weren't sending the event id through originally and it was working - will update and confirm if that fixes it. 

 ok  @greenart7c3  @Vitor Pamplona  @Derek Ross  @sourcenode we have a fix for this now - new version will be available in beta later today 

 Thank you for your hard work on this.