More info: I am pretty sure the issue is Bubble’s API connector not supporting 4-byte encoding. According to this Bubble used UTF-8 for character encoding, but doesnt specify how many bytes.
I experimented with my database and saw similar results when only using 3-byte encoding:
select CONVERT(temp USING utf8mb4) from temp where id=3 limit 1
Yields: "The stunning collection of 🔥10,000 AINightbirds🔥\nTech is the future, and NFT is the future of art!"
But select CONVERT(temp USING utf8mb3) from temp where id=3 limit 1
Yields: "The stunning collection of ?10,000 AINightbirds?\nTech is the future, and NFT is the future of art!"
Bubble folks - any ideas how to support fetching 4-byte characters??