Plugins created during the alpha are now available in the Plugin Marketplace and can be filtered with the new platform compatibility filter in the /plugins and editor plugin marketplace. There is no public release timeline yet for broader mobile plugin support or for mobile-specific templates and component library updates.
Users can still use custom server-side actions from your plugins within native mobile apps, but full mobile plugin development is not yet available.
I hope this answers your query. Please let me know if you have questions or clarifications.
I found this really misleading (deceptive?) - I bought this plugin to use it in a Bubble Mobile app, but it is not accessible in the Mobile Builder. Why are plugins being listed as “Web & Native Mobile” when they are NOT accessible in the Mobile builder?
This is Bubble’s doing I’m afraid. Plugins that have a visual element are not available in the native mobile builder right now, this is my understanding anyway. If any plugin has any server-side actions included then I’m pretty sure you can still access those.
The main difference between the two is “where the code runs”. Server-side actions will always run on Bubble’s servers and have no impact on the possibility of breaking anything that might stop your app from being published on either Google Play or Apple stores.
Visual elements however, pretty much always runs code directly inside the browser so that could stop your app from being published. I’m not 100% sure on that but I suspect this is the reason why you can’t see it and the reason why Bubble may have prohibited it.
Thanks. I understand that it could work in the “web view” but this should not be allowed to be classified as “native mobile” (presumably all plugins would fit that criteria).
I understand this may be bubble’s doing, but it needs to be addressed as it is confusing to those of us now trying to create native mobile apps.
I am truly fed up after writing the right MIME (video/mp4) and still the video from the Google Drive refuses to play. Please I need help here…every other platform link works, except Google Drive (and it’s not about API stuff here…just MIME frustrations, despite being the right one!).
Can you pop a Google API key into the plugin settings (through your App’s plugin area) and then retry it. It used to work without the key but that may have changed now. I managed to get your video working with the key.
Thanks again for your help last time I finally managed to purchase and install the plugin – the issue was that I hadn’t configured billing in Bubble. Just sharing this in case anyone else runs into the same problem.
Now I have another quick question: I created my Mux account and generated a token (Access Token ID + Secret Key).
I’d like to use the Create Asset (MUX) action but I’m not sure exactly where to place my ID token and Secret Key in the plugin setup.
I tried putting the Access Token ID in the Create Asset MUX – Authorization (header) field and the Secret Key in the field right below it, but I got this error:
The service Endpoint: - Create asset (MUX) just returned an error (HTTP 401 Unauthorized request)
Could you please confirm exactly where I should enter my Access Token ID and Secret Key for the plugin to authenticate correctly?
I’m having an issue sending videos to MUX using the latest version of your VideoJS Advanced + MUX (All Media) plugin (v1.386.0).
Here’s what I’ve done step by step:
I’m building a mobile app with Bubble App Native.
I installed Camera Capture for Bubble Mobile and File Uploader Pro Native Mobile to record or select videos.
In the MUX plugin, under Create Upload URL (MUX) → Authorization header,
on the top line I entered: Authorization
on the bottom line I entered my MUX token encoded in Base64 (format: Basic XXXXX...).
In my workflow I added: Event: Element Event → Camera Capture A → on Video Captured Action: Endpoint → Create Upload URL (MUX)
Is this the correct setup?
After that, I can’t find any “Upload media to MUX” action (like in your 2021 post).
There’s also no visible MUX element to place on the page, nor any field where I can send the video to the MUX URL (data.upload.url).
Could you please confirm:
What is the proper sequence of actions to upload a video to MUX in the current plugin version?
Has the “Upload media to MUX” function been removed or replaced by another method?
I really need this functionality to finalize the video publishing feature in my mobile social network app.
Thanks a lot for your help and for your amazing work on these plugins — they’re truly essential for Bubble native apps
In the plugin settings, for Create Upload URL (MUX) → Authorization header
Put both of those as: Basic
(so replace the word Authorization)
That’s used for the Authorization header value in the respected API call. One of those is used for the action, the other one is used under the “Get data from external API“ operation, which is the reason why they’re duplicated. I should have set all these MUX calls up with a shared Authorization header value, which I may change soon.
In your workflows, these are correct. You first need to create the “upload URL” then you pass that along with the file.
Event: Element Event → Camera Capture A → on Video Captured Action: Endpoint → Create Upload URL (MUX)
Typically, you would then need to run the “Upload media to MUX” action afterwards, but in your case, you already have the file so you don’t need to run this action. It doesn’t allow you to use a file from elsewhere at the moment.
When your “on Video Captured” event triggers, where is the file? This will determine what you need to do next. If it’s been automatically uploaded to your S3 storage, then you can pass the URL directly into the API call: Create asset (MUX). You wont need to generate an upload URL if you use that, so you can remove that part.
If you do end up using that, don’t forget to put the same Auth token values into that section under the plugin settings.
First of all, thank you so much for your quick replies and all your help — I really appreciate the time you take to explain everything clearly
Regarding your question about where the file is located after capture:
When the “on Video Captured” event is triggered, the value I get in media URL looks like this: file:///var/mobile/Containers/Data/Application/.../Library/Caches/ImagePicker/...mov
So it seems that the video is still stored locally on the user’s device and hasn’t been uploaded to S3 yet.
In that case, what should I do?
Because when I run the “Create Upload URL (MUX)” action, I don’t see any “Upload media to MUX” action available afterwards, so I’m not sure how to actually send the video file to MUX.
I finally managed to purchase and install the plugin – the issue was that I hadn’t configured billing in Bubble. Just sharing this in case anyone else runs into the same problem.
I created my Mux account and generated a token (Access Token ID + Secret Key).
Event: Element Event → Camera Capture A → on Video Captured
Action: Endpoint → Create Upload URL (MUX)