Test app's array not visible in plugin's update

i am writing a plugin. it shows up in my test app. it has a problem. in update, it looks at an array of objects to see if it is hydrated (contains any objects). the array is defined correctly in the plugin (i think), and setup properly in the test app’s properties view (again, i think). BUT, no matter how long i wait (asynchronously) for the array to be ready, it is always undefined (hence my “i think”). i’ve checked, rechecked my configurations, deleted and re-added the plugin, and numerous other tactics. none have succeeded so far. i could use some guidance (I asked AI but it’s training data is, well, obviously full of misinformation, sigh). I’ve been at this issue for about five days and could use some sane advice. ;-p

NOTE: in my plugin, the array is defined in Fields. so far so good. HOWEVER, in the Type field for the array, the actual type (defined in the test app, and yes, that test app is configured as having permission and is linked properly, I think, yet again) does not appear in the dropdown. Closest menu item is “any thing”. In the Editor field, i chose Dynamic Value as all the other menu items either are obviously not right or, App Type which does not give me a way to choose the specific Type.

Sounds like you are building your own plugin. Add console logs to the code to debug each and every step to see what is the issue.

gosh, is this an AI generated (or otherwise automated) reply? i did add lots of log statements, and did my best to summarize my findings in enough detail to be convincing that i indeed did a lot of it. my question to you: do you (or anyone on this forum) know about hydration, lifecycle of a plugin (initialize, update, internal state, access) and other undocumented subtleties that bear on sending data structures from an app’s database into a plugin?

Gosh, no it is not, it is just me giving you free experienced advice on how to find the root cause of your issue so you can post it and get more targeted advice on what you are doing wrong.

The use of ‘I think’ for me is very different from ‘the console logs I added to my plugin code for debugging is showing me abc’…and the complete lack in the entire post referencing any use of console logs in the plugin code does not indicate that you did ‘add lots of log statement’ and so therefor, maybe for you was enough to be convincing, but for me, it did highlight that there most likely are zero console log statements in your plugin code.

Yes I do. I’m sure others do as well.

My request of you: Show the screen shots of the console log statements in your plugin code and show the console logs in the developer console so as to demonstrate to others on the forum what the issue might actually be.

When you are as frustrated as somebody is when dealing with an issue like you are for as long as you are, it is easy to carry that frustration over to others who are just trying to be helpful and offer free advice to help you fix your problem.

1 Like

point taken. my apologies. in this day and age, lots of companies think their customers will fall in love with tech support driven by AI. enough said?

can i give you the urls of my test app and its edit page, and my plugin edit page? in the latter, I have added only two functions and a small handful of fields. no actions, very few tricks yet. in the test app, i added only the plugin and one workflow.

Here is the console output:

Mathew,

Point taken and welcome. I confess to being frustrated, kinda big time. I apologize. I hope you can help me as I cannot quite figure out from the dox how to fix my issue. I even hired a plugin expert and he could not fix it. Can you accept my apology and help me?

Jonathan Sand
Software Architect
sand@gizmolab.com

No worries, there is no need to apologize. My lack of response was not due to your expression of your frustrations. I didn’t respond because the help you are requesting goes beyond a forum post response and is not the type of problem that I take on for client work.

You should try reaching out to some plugin developers that promote themselves as such. Those would be the types that actively build plugins for others or perhaps help teach others how to build them.

might i inquire why bubble as a company provides rather little support for people adding to your plugin marketplace, making the bubble ecology more robust and versatile. I for one have encountered many serious gotchas. serious? most of them take days of research and trial and error. AI is miserable at it due to lack of material on which they are trained. plugin developers are way beyond my meager budget. this latter puts a high barrier to entry for serious minded folks who are not part of the deep pockets corporate world. sigh.

ah, yes, no reply. another sigh

You’re gonna have to share your init and update code for anyone to help you debug. None of the links provided work anymore.

This has been the way for years. You can file a bug report if you believe that the issue is Bubble related. Issues related to the plugin code itself is the responsibility of the builder.

Bubble plugins aren’t meant for casual users :sweat_smile: so Bubble does not dedicate many resources to plugin builders. Which is a pain since the docs do miss a few edge cases but nothing that a decent dev can’t figure out.

Bubble dev is pretty niche, Bubble plugin dev is a niche in a niche. So there wasn’t much to scrape during training. You’ll need to add your own instructions as context.

You can try my AI instructions. They’ve been working for me reliably so far.

1 Like