Bugs found on mobile app building

It has been a frustrating experiance when come to mobile app building using ReTool. It look like a half-baked product without many documentation can be found.

  1. The hamburger menu appear on first screen only. However, when we do a navigation back to Home screen (first screen), the hamburger menu disappear, replaced by a back button.

Imagine after you done many actions from screen to screen, how many time I need to click on back button to get to the hambuger menu?

  1. I have 2 screens, for some weird reason, the moment I launch the mobile app, it go direct to 2nd screen, and when I click on back button, it go to first screen again, and everything back to normal.

  2. This reported before, the moment i delete the tab bar, all my screens gone missing.

regards,
vic

Dear team, please see the video here:

https://www.awesomescreenshot.com/video/32868799?key=d67544400a528ac03e68fabee3496f1b

00:13 - It jump from first screen to 2nd screen even at edit mode
00:22 - I clicked the first screen, the screen name changed at Inspector panel, but the UI/UX not refreshed
00:29 - I deleted the 2nd screen, however if you continue to watch, all the components at first screen are still there... but the first screen is entirely blank

I develop the mobile app using ReTool around a year, I never have such buggy experience untill recently.

Hi @victor.tai,

Thank you for taking the time to record these bugs. I'm sorry to see you're running into multiple issues with navigation in our Mobile product. I shared your feedback regarding the back button design choice as well as reported the two bugs you've shared. I'll comment here with any updates. Thank you!

I'm also experiencing this issue, and it's very frustrating.

When I try to duplicate a button, it ends up wiping out 20 objects in a different view.

I can add a new button, but as soon as I try to rearrange it, all of the objects disappear.

It’s a wild bug.

I've tried using private mode to ensure there weren't any plugin conflicts, and I've tested it across multiple browsers. I've even tried duplicating the app, but nothing works. I can't touch this app at the moment, because whenever I do, it completely breaks.

I can send a video too or provide detailed instructions on how to replicate the issue within my app. Just let me know.

+1 experiencing these bugs

Hey @victor.tai and @Derek_Watts,

Could you send me your app export ? so we can repro this on our side to take a look.

2 Likes

No problem James, I sent it over.

It has a lot of resources attached, so let me know if you'd like to see this issue within our environment.

@victor.tai any luck getting this resolved?

@Derek_Watts

Nope, I change another method, lucky for me enough, it was a simple mobile app for simple task. However, it is still frustrating to see the mobile app editor don't work like normal retool app

@james.lee any luck diagnosing this issue?

@james.lee, just checking in – have you had any luck with the issue? Retool Mobile seems to have a significant problem right now, as @victor.tai mentioned earlier. I understand bugs are part of the process, but this one’s really preventing me from moving forward with my project. Any updates or workarounds would be super helpful. Thanks!

We're currently working on a fix for the navigation issue that @victor.tai reported earlier in this thread.

The problem stems from the 'detail screen', where if you choose a 'detail screen' from the tab bar, and then rename that screen, the app gets into a bad state.

The workaround is to select the desired detail screen again and then refresh the browser.

I haven't looked into the other bug yet (the duplication one)

1 Like

@Robin_Pham in my case, its duplicating the object, adding new objects or rearranging objects, they all cause objects to disappear.

Thanks @Derek_Watts for reporting, we've found the bugs and are going to deploy out fixes soon (next couple of days :crossed_fingers: !

2 Likes

@Robin_Pham any luck getting this bug fix deployed?

Thanks so much

Looking into this now and will have an update for you shortly!

1 Like

The earliest the bugfix will appear is in 3.116.0, but it may be on a version or two after that. Thank you for your patience!

1 Like

Hey @AbbeyHernandez & @Robin_Pham

Just wanted to confirm that, based on my initial testing, this bug looks like it’s been fixed. Thanks so much for your help!

1 Like

Thanks for confirming!

1 Like