Whenever we place adjacent blocks to the air they become invisible

How are you placing blocks in the air to begin with? they need an adjacent block to be targetted.

I am placing adjacent blocks not non-adjacent blocks but still its happening

If you can, a recording of this would help.

You're saying that you're placing adjacent blocks to air, and in the image you're in the sky. How are you even placing the blocks in the sky with nothing around it? Are you using /setblock to place a block in the air?

Can you look at the block with debug (f3) on? What block does the debug say it is (on the right of the debug info). Do you have any resource packs on, that would affect the block?

I'm not using set blocks or anything i'm just like we dig straight down i'm building straight up and thats what is happening also i dont have any res packs Joshua

We do not have enough information to find the cause of this issue.

Please record a video of this happening and attach it to this report.
While recording this video, please enable the F3 screen.

If you are on Windows, you can use Windows+Alt+R to open a built-in app for recording game footage.
If you are on Mac (Mojave or later), you can use Shift+Command+5 to open a built-in app for recording your screen.
In case you don't have a program to record videos, we recommend using the free recording software OBS.
In case the resulting video file is too large to be uploaded to the bug tracker directly, please upload it elsewhere (e.g. as unlisted video on YouTube) and link to it here.

_{This issue is being temporarily closed as Awaiting Response. Once the requested information has been delivered, the report will be reopened automatically.}

Quick Links:
📓 Bug Tracker Guidelines – 💬 Community Support – 📧 Mojang Support
📓 Project Summary – ✍️ Feedback and Suggestions – 📖 Game Wiki

i have uploded the recording of it

Try it without mods (optifine is installed).

It still happens without optifine

I cannot reproduce this issue in 1.19. Could you please provide some additional screenshots or videos of this issue occurring whilst the F3 debug screen is enabled, and whilst running a complete vanilla instance of Minecraft. This would assist in diagnosing the potential problem here. Thanks in advance.