Originally Posted by
gormless
Yes, same for me.
Got a new phone, thought it was caused by the new one but fails on the old phone as well.
OK, BA: here's the issue. Your developers need to fix this.
Here's the system log from my phone:
********** PLEASE READ ************
*
* New versions of the Android SDK no longer support the Crypto provider.
* If your app was relying on setSeed() to derive keys from strings, you
* should switch to using SecretKeySpec to load raw key bytes directly OR
* use a real key derivation function (KDF). See advice here :
*
http://android-developers.blogspot.c...ecated-in.html
***********************************
Returning an instance of SecureRandom from the Crypto provider
as a temporary measure so that the apps targeting earlier SDKs
keep working. Please do not rely on the presence of the Crypto
provider in the codebase, as our plan is to delete it
completely in the future.
So, the BA Android app is using a deprecated API and has gotten away with it until Oreo release. Seems the developers need to get working on a fix.
What Android version are other people seeing this error running?