I emailed support with my information. Thanks. I also found a different flash drive and Prime read it. I assume the first drive wasn’t reading because it had a img. file of Tails OS or because of the type of format. Note Android was able to read the drive.
1 Like
Thank you. I have replicated the issue after disconnecting and reconnecting and have filed a bug report with our engineers.
1 Like
Any feedback on my issue? I still have a unusable device
Looks like we have a potential fix in QA right now and scheduled for the release after next. I’m going to see if I can grab you a custom testflight link to unblock you.
@Panicseller contact support with your apple ID and I’ll get you a TF build to try out.
Any feedback on my issue? The Android 11 issue.
I still have a unusable device
Looks like we have a potential fix for yours also in QA right now and scheduled for the release after next. I’m going to see if I can grab you a custom Play Store link to unblock you. Can you contact support with your Google ID please?
1 Like
I will fire off an email to support right now. Thanks.
1 Like
I mailed them already end of march with the logs, they were looking into it but no reaction so far. Why should I have to give an apple id?
As I mentioned in my previous post, we want to send you a testflight build to see if the fix we have resolves your issue. Its completely optional. If you don’t want to install it, it just means you’ll have to wait a while before the main release is submitted to the app stores.
Got it. Could you help me understand why it seems most users have no issue on iphone but I do?
The short version: Envoy was asking iOS for the Bluetooth manager slightly too early in the app’s startup, before iOS had finished bringing its Bluetooth stack up. On most devices iOS happened to already be ready, so it worked. On yours, for whatever timing reason, it isn’t - and the manager comes back as “not available or not powered on”, which is the NO_CENTRAL error in your logs. The fix changes when Envoy initializes that manager so iOS has time to be ready first.
We can’t say for certain it’ll fix your specific case until you actually try it, which is why I’d love to send you a TestFlight build to verify before it ships to everyone. Completely your call though - if you’d rather wait for the public release, that’s fine too.
1 Like
Interesting, if the time difference is small I don’t mind waiting, otherwise open to trying it out on testflight.
We just released 2.2.13. Your fix will be in 2.2.14 which might be a few weeks.
Is there someway to sideload your Android 11 fix since google wants to review it first, I trust you guys.
There is, but the main issue is us sharing a public APK file that has not yet gone through QA and is easily shareable. Not saying you would, but the Play Store option removes that risk.
1 Like
About the arrow - tapping anywhere outside the keybaord in any screen where the keyboard is present should minimize it