Hi, any idea of what can be causing this warning?
1 Like
Hey @pachocastillosr
I´m getting that error as well all the time.
@josh do you mind taking a look or letting as know if this is expected due to some update or something like that?
1 Like
Hey! Good to see I am not the only one. I just filed a Bug Report | Bubble. It might be useful if you file one exposing your case too.
I believe that this is on Bubble’s end because I tried restoring my app to a time where it presented no warnings or errors and the warning still appears.
The warning started appearing on February 3rd, 2022, around midday (UTC-5). I tried running my app on Safe Mode (How to Run Your App In Safe Modes | Bubble) and it is still appearing.
1 Like
I’m seeing the same problem. No problems yesterday. The problem started to appear as soon as I started debugging today.
2 Likes
Yeah, this warning seems to be new today. I can trigger it with the following:
The object stored at Karter A’s ITEM 6 Value is a geographic address. Now, like a Thing, a geographic address doesn’t have a default text representation, but yesterday, writing this value would silently fail while today it generates warning. I don’t think this warning is particularly helpful and wish it would go away, but that’s just me.
The circled thing is Text Q in the page, BTW, and the warning output is as follows:
Yep seeing this warning on blank data as well.
Same, I’m getting this recently too
Oh yeah, that’s also happening in my example. Some of those expressions are empty.
(What’s going on with that is that “empty” is actually the JavaScript value null, which is a special object which has no properties at all. Bubble’s dumb warning code is firing when anything we ask to publish to the text element is an object, basically. 50 Shades of Derp, over there.)
1 Like
same thing happened to me today.
Now this new error is suddenly happening in my app (Error: an error occurred trying to evaluate this property)
Maybe it is related to this warning, they both talk about “Property”
I am getting numerous such “General” warnings 
not sure how to clear it! @emmanuel
I’m having this issue as well. Seems to be a major bug since content is missing from webpages.
Hi everybody,
Just wanted to update you on my bug report case.
I just finished chatting with Colin Johnson (he was very kind and solved the problem, at least in my case) from Bubble support. He told me that they have reverted one of the changes they did that might have caused the errors.
Hey Francisco,
Just wanted to give you a heads up that we have another change that’s causing some issues that went out at a similar time that may be causing the functionality differences instead of these warning messages. Our engineers have already run a revert of that if you wouldn’t mind testing out one of these behaviors one more time?
Apparently, my app is no longer showing any functionality problem any more. However, he told me that this warnings will keep appearing.
These are only intended to point out potential sources of unexpected behavior like a low level information or warning log message in the browser console.
I hope that the problem is solved for your apps as well!
1 Like
This bug is still causing breaking issues in my app, in particular I’m using the expresion plugin to create values for me (everywhere I have the expressions are generating the same error) and anything that is dependent on those values are broken. Are you saying the problem is gone for you now?
1 Like
Hey,
This issue is still showing in my case. Any news anyone has about this?
Thanks a lot.
2 Likes
Hi, yes, my app is still showing the warning but its no longer interrupting it’s functionality, its not broken anymore.
I suggest you file a Bug Report | Bubble, maybe there are other updates that they can revert and fix it
Same problem here 
Hahaha. Does this mean Bubble is going to be strongly typed now? Will we all have to learn TypeScript?
Uggh! I’m sure you meant this as a joke. 
1 Like
I also started seeing this warnings… though, what I found is that in the prior versions of Bubble a [Click] was present prior to any text I wrote explicitly. If removed the warnings go away.
4 Likes