There are two bugs here that we need to resolve. One is a regression preventing the component from upgrading and the second is an issue with the update of the Bluetooth components to SDK 31. The former should be a quick fix (you can also hand edit the project file to "upgrade" since it is so trivial) but the latter is going to take a bit more work on our end.
Edit: these two issues are now being tracked.
opened 11:39PM - 26 Sep 22 UTC
issue: accepted
status: forum
affects: master
priority: high
regression
**Describe the bug**
<!--
Describe the bug in sufficient detail so that we c… an understand the issue. You should also describe the steps to reproduce the issue (below) so that we ideally can confirm it.
-->
[From the forum](https://community-appinventor-mit-edu.ezproxy.canberra.edu.au/t/bluetooth-conection-problem-fail-message-in-the-browser/66107?u=ewpatton): Loading an existing project with a BluetoothClient component causes an error about upgrading. I believe this was the result of a path being dropped in YoungAndroidFormUpgrader.java because versioning.js does have an upgrader for version 7 but the former does not. A property was added so the upgrade is a trivial one.
**Affects**
<!--
Please check off the part of the system that is affected by the bug.
-->
- [x] Designer
- [ ] Blocks editor
- [ ] Companion
- [ ] Compiled apps
- [ ] Buildserver
- [ ] Debugging
- [ ] Other... (please describe)
**Expected behavior**
<!--
Please describe what you expected to happen before you encountered the bug.
-->
The upgrade should proceed normally.
**Steps to reproduce**
<!--
Please describe the steps needed to reproduce the bug. If possible, please include a minimal example project that demonstrates the issue.
-->
1. Create a project with a BluetoothClient in nb189 and then load it into nb190.
opened 11:42PM - 26 Sep 22 UTC
bug
issue: accepted
status: forum
technical debt
affects: ucr
priority: high
**Describe the bug**
<!--
Describe the bug in sufficient detail so that we c… an understand the issue. You should also describe the steps to reproduce the issue (below) so that we ideally can confirm it.
-->
[From the forum](https://community-appinventor-mit-edu.ezproxy.canberra.edu.au/t/bluetooth-conection-problem-fail-message-in-the-browser/66107?u=ewpatton): When using blocks like Connect on Android 12, we must first ask for user permission for BLUETOOTH_* permissions. As a workaround, people can go into the settings app and grant permission that way.
**Affects**
<!--
Please check off the part of the system that is affected by the bug.
-->
- [ ] Designer
- [ ] Blocks editor
- [x] Companion
- [x] Compiled apps
- [ ] Buildserver
- [ ] Debugging
- [ ] Other... (please describe)
**Expected behavior**
<!--
Please describe what you expected to happen before you encountered the bug.
-->
When a Bluetooth request is made to scan, connect, or advertise, permission must be asked of the user on Android 12+.
**Steps to reproduce**
<!--
Please describe the steps needed to reproduce the bug. If possible, please include a minimal example project that demonstrates the issue.
-->
1. Create a simple bluetooth app on Android 12. Using any of the connection blocks will fail with a permission error.
1 Like
The issue related to the upgrade message has been fixed in nb190a. The other issue related to permissions is in progress.
The BluetoothClient/BluetoothServer permission issue should be addressed on this temporary test server: http://nb190a-bugfixes.ai2-ewpatton-temp.appspot.com/
My bluetooth application works well using this test server (I had above mentioned problems before). When will the problems be fixes in the standard server?