Hi everyone, I’m trying to build a booking system in my mobile app. I installed Zeroqode’s Bubble Mobile Bundle (I tried just installing the booking plugin first but the element wouldn’t show up in my app…) and am using the Available slots element. I believe I have everything set up correctly, I checked the demo and documentation, but when I make a short list or vertical list and have it display the available slots, the data appears for half a second then disappears. I can’t debug it very well because Bubbles date/time picker doesn’t work in the preview debugging window (would be nice if it did). I attached some photos. I checked privacy rules also but they seem fine. I’m not sure why the data is loading and then disappearing! Thanks for any help.
Hi there
It would be helpful to see a screen recording of the disappearing behaviour on your app (you can use the Bubble Go app to preview it on your real device for iPhone here or Android here).
The Preview window for Bubble Native isn’t great at the moment, so using Bubble Go is a better way to test.
Reece from CreatorConcepts
Hi @boothmate,
Thank you for reaching out and providing those detailed screenshots! It’s great that you’ve already cross-referenced the documentation and demo; that helps us narrow things down significantly.
When data appears briefly and then vanishes in Bubble, it usually indicates that the element is successfully initializing, but a subsequent change in its input parameters (like a null value or a privacy rule restriction) is forcing it to clear the results.
Here are a few steps to help us troubleshoot this:
1. Check for Null or Empty Inputs
The “Available Slots” element is very sensitive to its input parameters. If any of the following are empty when the page finishes loading, the list may disappear:
- From/Until Dates: Ensure your
Date/TimePickerhas a Default value (likeCurrent date/time). If the picker is empty on page load, the element has no range to calculate, which can cause the slots to vanish once the “initial” empty state settles. - Bookable Hours: In your screenshot, you’re pulling availability from
Parent group's Service's consultant's availability. If the “Service” or “Consultant” hasn’t fully loaded yet, those values return asnull, causing the element to show no slots.
2. Verify Privacy Rules for Related Objects
Your screenshot shows privacy rules for the User type. However, the plugin also relies on the Service, Availability, and potentially the Booking types (if you are using the “Booked slots” field).
- Check the Service and Availability types in your Data tab.
- Ensure that the “Everyone else” rule (or a specific rule for the logged-in user) allows them to “Find this in searches” and “View all fields” for the attributes you’re using (like
Monday:min,Monday:max, etc.).
3. Data Format for Availability
The plugin expects the “Monday from/until” fields to be in a specific format (usually a number representing minutes from midnight or a specific date/time, depending on your setup).
- Double-check that the
consultant's availability's Monday:minactually contains data in your App Data tab for the specific consultant you are viewing. - If those fields are empty in the database, the element won’t have any “working hours” to generate slots within.
For more detailed setup instructions, you can always refer back to our official documentation here: Calendar Booking & Time Slots Mobile Docs.
Could you please confirm if the “Service” and “Consultant” data is definitely loaded in the Parent Group before the element tries to display the slots?
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi @boothmate,
I just wanted to follow up and see if you’ve had a chance to check the input parameters and privacy rules we discussed.
Is the “Available Slots” element working correctly for you now, or do you still need some assistance?
Best regards,
Support Team
Browse all Zeroqode Plugins for Bubble
Hi, thank you for your response. I did get it working, although I’m not exactly sure what fixed it. I gave the short list element a condition to only load when the item count is less than 100 and it’s working now. Maybe it was getting overloaded with too many slots and crashing?