Problem: Bambu Handy immediately crashes when opening
Bambu Handy Version: anything newer than 3.6.0
Platform: Android
Steps to reproduce:
Open Bambu Handy
It crashes
Screenshot: Not Applicable
Other information: Android 17 QPR1 Beta 4, Pixel 9 Pro XL
And now Google released 17 stableā¦.
Missing the actual layer number being printed in Handy. The % done is nice but we really need the actual layer number if there is any manual intervention (captive nuts, etc) required in a print.
Also, now it seems thereās extra steps to monitor temperatures as well.
I may not have the most up to date version but having issues with trying to increase or decrease rolls in inventory. What am I missing?
See my earlier reply with the formal report layout.
+1
Yes, please add it back to Handy
It would be great if you finally fixed the Bambu mobile app for Android 17 Beta. This issue has been known for weeks now. It is simply unacceptable that there hasnāt been a single statement or any information regarding this.
Android 17 QPR1 Beta 4
Build-Number: CP31.260522.006
Bambu Handy Version: 3.22.0
Bug:
The app starts up to the splash screen and closes after one second.
@SupportAssistant @BambuLab has anything ever been done about this on your end? The app hasnāt been working for me for months!!!
Problem: The āCustomizeā button in Bambu Handy returns a 404 error when the app language is set to Traditional Chinese (ē¹é«äøę). The button works correctly in English and Simplified Chinese (ē®ä½äøę).
Bambu Handy Version: 3.23.0
Platform: iOS
Steps to reproduce:
Open Bambu Handy and go to Settings, set the language to Traditional Chinese (ē¹é«äøę).
Navigate to a model page that has a Customize option.
Tap the āCustomizeā button.
Observe that a 404 error page is displayed instead of the customization page.
Change the language back to English or Simplified Chinese and tap the same button ā it works correctly.
Other information: iOS 26.5, iPhone 12 Pro Max
Version 3.23.0 has been released, and it still doesnāt work on the Android 17 beta!!!
Are you kidding us ?
When the ā ā ā ā are you finally going to fix this bug?
Iām just getting sick and tired of this.
Problem : Handy App (June 25 2026) feature to add filament to the library by scanning the barcode on the sticker on the Bambu filament box - is NOT working. No data gets filled in on the form.
What I get is the filament dialog opens with no data in it other than the ānameā has been pre populated with the date and time of day.
Handy app version; 3.23.0
Platform : iOS 26.5
Steps to reproduce :
open handy app, Devices tab
Scroll to bottom to Filament Library , select Add Filament
Select method - scan to add , scan the barcode portion of the sticker on the flap of the cardboard box the filament is inside of.
indeed. This is very frustrating. Havenāt been able to use handy for bout 4 months now
Problem: Cannot interact with filament selection dropdown ā cannot start any prints
Bambu Handy Version: 3.23.0
Platform: Android (17)
Steps to reproduce:
Open Bambu Handy
Choose any model, āPrepare to printā, and choose a profile
The āMy filamentā dropdown is totally non-interactive; no amount of tapping anywhere on it will let me choose a filament.
Pressing the āPrint current plateā button will make the āMy filamentā dropdown flash, indicating that a filament must be selected to continue, but filament selection is still broken.
Screenshot:
Other information: Printer is an A1 mini, no AMS
Use a non-beta version and everything will be fine. Theyāre not going to bother fixing the beta problem. Are you perfectly removing the supports of a failed print?
Whiteout beta testers nothing would work thou, and bambu ignoring that it does not work with beta for months is a relatively bad thing. The version we are running now is 3 months of public release. Would you rater we didnāt report it?
The problem with the Android Beta is still existing. The last release to work is version 3.0.6. There is the possibility to stay on that release. But the report is important as in a couple of months noone is going to be able to use the app if they donāt fix it. It seems that they are still relying on virbox and Android 17 is rigourosly blocking those certificates. So it seems that everyone is going to have that problem if they do not adress it.
Itās not just the beta.
I have a pixel device with an official release of Android 17 and I have the same issue. This is unacceptable, itās a major loss of functionality for a device I just purchased a couple weeks ago.
