Views can have properties, like RUs! Yay! But how do I actually get the property? The view itself isn’t available in the data source… also not seeing any equivalent of Current Page's Thing…
EDIT: It was a glitch. Refresh and the View is available as a data source under elements as expected. Glitchiness has a HUGE impact on how people perceive Bubble, especially re: how easy it seems. A glitch like this could trip up a beginner for days.
Yo, do workflows triggered from clicks just not work? I’m getting 0% response from any workflows triggered from clicks. (Hard to be clear since the debugger doesn’t work.)
Update 1
Still working on this. I can get an action to partially happen if I click really fast after the view loads. If I wait too long, it won’t happen. Also, it doesn’t do animations, ever.
It’s possible that what I’m seeing is that values in Group VARs aren’t updating at all when the DB is updated? If so, I don’t think I can use mobile. Without functional variables you’re utterly crippled. But maybe that’s not what’s happening–maybe it’s the click that isn’t working. I still can’t actually tell.
Update 2
I’m so confused. The second button/workflow seems to work. The first one still doesn’t work (except the first time you click it, if you click it soon enough after the view loads). What on earth??
Update 3
Seems to have been caused by the presence of an animation action. Removing the animation action un-cursed the workflow. What a frustrating experience.
Update 4
Ok, so odd but when I fixed the first workflow by removing the animation action, the second workflow (which also had an animation and was previously working) stopped working, until I removed the animation action from that workflow. So it seems that only one animation action will curse your workflows, seemingly whichever one is oldest.
Yeah animations and shadows dont work right now. I agree, a debugger is desperately needed. We dont know of its a bug, an unsupported item, or just a workflow issue.
Returning to the issue with workflows… yesterday when I went to bed all the workflows were working fine. First thing I did today was make a video for a client and… half the buttons don’t work anymore.
Nothing changed except the tab. I’ve been using Bubble long enough to know that there are often ways to work around these types of glitches. Are there any elite native Bubblers who have figured out an approach to avoid stuff like this?
And BTW, it takes a very advanced user to be able to work around glitches. I know there’s a lot to consider when prioritizing, and one factor is “is there a workaround” but another factor to consider needs to be “expecting users to discover and implement workarounds is extremely beginner-unfriendly.”
Update:
Mea culpa. Turns out it was, in fact, me that broke it. I’ve hit so many roadblocks that I just assumed that it was Bubble’s fault instead of mine. This isn’t an ego thing. It takes a developer lot of skill and experience to be able to know when to keep trying to debug an app on the assumption that it’s the developers “fault” and when to stop on the assumption that it’s the system’s “fault.” Terms like “fault” make this feel like it’s a petty, emotional thing, but it’s an incredibly technical part of the debugging/diagnosis flow, and getting it wrong in either direction can waste huge amounts of time and effort.
Being new to a system (like I am with Bubble native) makes one less likely to get it right. But also to blame (and here I mean blame in the more traditional sense) is the bugginess/glitchyness of the system. If I, as a developer, run into a lot of glitches, bugs, and broken features, it’s my responsibility to adjust my tolerance for when I blame the system for problems. I must lower my trust in the system. But that runs the risk of false negatives, as was the case here.
All of this is part of the deal in a private beta. This is what I signed up for. But I’m hoping this feedback will stick in the minds of developers for when it’s released.
Each tab or view has totally different workflows. Im wondering if thats what caused this.
All elements collapse when hidden. This is what I want 99% of the time. Great default!
But sometimes, fully hiding an element breaks the layout, especially when aligning things using Space between container alignment.
Example: I want the page to be centered, even when the “next” and “previous” buttons are hidden:
But since they collapse when hidden, it breaks the layout:
I figured this wouldn’t be a problem since I could just use Align to Parent layout, but alas, that layout is not available. 
Edit
Not having Align to Parent is a real pain here too. The width can also change for other reasons that are harder to account for…
Thankfully Bubble is still flexible enough that you can get creative and still solve this. Hacky tho.
What I’ve been doingin this case, if i want an element to not shot but also not collapse. I modify the opacity and make the elemen not interactive
I am finding it really hard to create a layout on vertically scrolling views where there is something stuck to the bottom of the screen.
It’s easy on a not-scrollable view because the container group min-height can be set to 100% height and it will actually fill the height. Since this doesn’t work on a scrollable view, I can’t get something to be pushed down to the bottom unless the content actually pushes it to the bottom–but of course due to varying screen sizes I have no way of knowing the amount it needs to be pushed.
Why not just use a non-scrollable? Because dynamic content. Sometimes it might need to scroll, depending on the content length.
I just realized there’s both “Go to Tab” and “Go to View” … I don’t understand the difference, especially since pages show up for both…
Yeah for this ive been doing non scrollable view and then set the bottom group no max height and container layout bottom
@brenton2 Thank you for documenting your journey so clearly! We’re rolling out a new onboarding email series and would love to get your thoughts. I’ll reach out to you!
Getting further along here and I’m running into things that I just have no idea how to test before deploying.
The following don’t work on browser preview or Bubble Go:
I guess I just need to push my app to the stores. Sure hope that doesn’t take long!
I still haven’t fully read through the documentation on this. I skimmed it but I still have questions about getting my app on the official Android and Apple app stores:
Edit:
Yikes! I have to apply for a DUNS number to get my app on the app store if I register as a company??
Edit 2:
This Google Console application is kinda intense. Thought I was finally done and then:
So if I use the Request notification permissions action, will it pause the workflow there? Or will it do the other workflow actions continue in the background? E.g. will this just navigate away from the page before the user has a chance to accept?
Furthermore, is there any way to programmatically know if the user has actually enabled notifications? If they click “no” what happens later when I try to send notifications?
The documentation is not helpful here.
Wonder what the chances are that the result of that action is what the user’s response was? It’s a boolean…
This brings me to another question… is there a way for me to know whether I’m on the web preview, Bubble Go, or deployed? (And further, if I’m on iOS or Android?)
That would be helpful to write conditions to make the app work with fallbacks when I’m in web preview etc.
I started following steps to generate a keystore. The instructions are a bit verbose since they’re designed for people who aren’t familiar with terminal use. As someone who is, I just want to know what I need to do as succinctly as possible without fluff.
Also, in terms of being newbie-friendly, there needs to be a note that they may see errors or need to install dependencies before running the commands. E.g., the instructions say “Hit enter. The terminal will respond XYZ” but it didn’t. Instead, it responded like this:
The operation couldn’t be completed. Unable to locate a Java Runtime.
Please visit http://www.java.com for information on installing Java.
This is why terminals are daunting to most people, not because it looks scary. You can put answers in for this particular issue but there are infinite combinations of hardware/software and potential errors. I think a friendly note saying that it’s possible to work through the errors with the help of Google, an LLM, or the forum, would go a long way towards setting expectations for people.
EDIT:
I finished the instructions to create the keystore. The last thing the article said was:
Your keystore file has now been saved to your computer, and is ready to be uploaded to the Bubble settings page.
However, when I went to Bubble Settings, I could not find anything that seemed to be related to this. Perhaps I’m looking in the wrong place. Where do I upload this file? Is it just using different terminology?
None of these scream “keystore” to me… but maybe…?
General settings
App display name
App icon
Splash screen background color
App SchemeApple settings
Bundle ID
Team IDApp Store Connect API
Key ID
Issuer ID
Private keyApple Push Notification service
APNs key ID
APNs keyAndroid settings
Package name
JSON key
Code signing key
Code signing key alias
Code signing key password
Deploy track
Release status
Firebase Cloud Messaging
google-services.json
Firebase service account key
Just realized that iOS and iPadOS are different. I am assuming/hoping that Bubble builds for both?
Edit: yes, it will work on iPadOS, it just may not be optimized for it.
For now, it’s iOS only
Hm, this gives me hope that it could work on both iOS and IPadOS.
Edit:
Got word that it will work for iPadOS, it just won’t necessarily be optimized for it. Yay!
Diligently going through the steps to set up Android/Apply accounts.
After creating the app in the Apple App store, but haven’t yet put any info into Bubble about this Apple app, nor given Apple any info about the Bubble app, the instructions suddenly end with this last section:
Like, hold on a second! “Once your project is set up?” That’s what I’m working on here, you’re supposed to help me through that! I feel that you have left out some steps!
