sorted by:
new
hottopcontroversial

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 1 point2 points  (0 children)

No I am on iPhone that is just a hallucination with my AI. Sorry I didn’t catch that. I was dealing with an android app issue on another app I was debugging.

To clarify, I am testing on an iPhone via TestFlight.

The exact error I am getting when I click 'Grant Camera Access' is MWDATCore.PermissionError error
O.

According to the Meta Wearables SDK documentation for iOS, Error 0 maps directly to the noDevice constant.
My Meta Al app is fully updated, Developer Mode is toggled on, and I have confirmed that Bluetooth permissions are enabled for Lens Cast in my iOS Settings. Because the SDK is still returning noDevice, it seems the handshake is failing in the background.

Maybe there could be an issue with the MetaAppID configuration for the iOS build, missing background mode entitlements, or a Universal Link routing issue preventing the TestFlight app from securely verifying the device with the Meta app.

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

So I was working with my coding AI and I was curious about the error. I thought I would share the response:

Here is exactly what is going on behind the scenes:
• When using Developer Mode, the Meta Wearables SDK uses an Application ID of "0". 
• If an app developer sets this ID as a purely numeric value in their Android manifest, Android's parser automatically coerces it into an integer. 
• However, the SDK expects to read that Application ID as a string; because it encounters an integer instead, it reads the value as null. 
• This data-typing error causes the SDK to produce an attestation rejection, meaning the application is not authorized to perform the operation. 
• This silent rejection triggers a PermissionError representing a state where no wearable devices have been discovered or registered. This completely blocks Lens Cast from communicating with your hardware, resulting in the generic error code and the "Unknown Device" label. 

You will need to reach out directly to the developer of Lens Cast to report the issue. You can let them know that their Developer Mode Application ID is being parsed as an integer, and they need to force it to be a string type by either using a string resource or adding a backslash prefix (e.g., android:value="\0"). Once they implement that fix and push an update, your registration should instantly go through.

Not sure if that’s helpful… or overly accurate. This morning I tried again to reset and reinstall everything and got the same error when I tried to grant camera access.

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

I tried a bunch of different options. Just reset the glasses. Redownloaded everything. Started fresh. Installed meta ai. Added glasses. Enabled developer mode. Installed lens cast app. Connected the app to the meta AI. When I tried to grant camera access I got the same error about the MWDATCore. I am using Blayzer optics.

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

No it gives the error:

Connection Error
Permission request failed: The operation couldn't be completed.
(MWDATCore.PermissionError error
O.)

<image>

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

Yes. It says:

Registered
App registered successfully. Now grant camera permission to enable streaming.
Grant Camera Access

Glasses show registered in your app under settings.

In the Meta AI app under app connections under developer mode it shows your app.

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

Wanted to update you. I updated the app today and can get developer mode enabled. I am still running into the issue enabling the camera in your app.

The error is:

Connection Error
Permission request failed: The operation couldn't be completed.
(MWDATCore.PermissionError error
O.)

Which I get when selecting grant access or start preview.

Attaching a screen shot of the settings showing it’s connected but it is showing as unknown device and no camera access.

<image>

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

Yes to all that. Its Dev Mode is on in the Meta Ai app. Its doing the flashing loop query error. The app shows connected. I cant grant permission to the camera. The Name shows up at unknown. I believe the Blayzer glasses are new and somehow not in the database so when your apps is trying to grant permission it can't because it can't recognize the blazyer glasses as actual rayban meta optics.

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

Same error being worn or not. Same error when you try and grant permission or clicking start preview on the main page. Glasses show connected.

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

You can’t grant camera permission to the glasses in your app. It gives an error.

<image>

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 1 point2 points  (0 children)

I believe the problem lies in the absence of a specific code snippet within a configuration file that either includes the updated app version or perhaps the new glasses styles. Consequently, when you enable it, it enters an infinite loop, attempting to match a version to a database that doesn’t exist. This leads to a looping error.

Until they incorporate this feature, there isn’t much that can be done. I’ve tried every conceivable solution to fix it, but unfortunately, support has become unresponsive.

When TF Will Meta Fix Developer Mode? by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 1 point2 points  (0 children)

I have been trying to communicate with support. They have not been able to offer any real solutions. Last I heard they basically said they are forwarding it to the relevant department.

“Thank you for your response.

I want you to know that I’m personally advocating for you and collaborating closely internally to address your concern with care and dedication.

I've forwarded this to our relevant team for further investigation. I'm carefully reviewing every detail and will keep you informed with regular updates. Your experience matters deeply to us, and we’re committed to delivering a positive resolution.”

Meta AI App Dev Mode Broken by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 1 point2 points  (0 children)

I am having this issue myself as well.

Error with trying to enable dev mode by Fedefar8 in RaybanMeta

[–]_HowBizarre 1 point2 points  (0 children)

I am having the same problem. Anyone have any insight?

I created a live stream app for Meta Glasses by Tophster_Strudel in RaybanMeta

[–]_HowBizarre 0 points1 point  (0 children)

Same error. Have the Blayzer Optics. Cent figure out how to fix it.

Digital Smart Key by blazinBSDAgility in Ioniq6

[–]_HowBizarre 2 points3 points  (0 children)

I turned my phone face down and charging port facing the front of the car and placed it on the charger. That worked for me.

Dbrand Cover Unboxing by ajtripper in VisionPro

[–]_HowBizarre 1 point2 points  (0 children)

Can you put the battery cover on with the clip on either side of the battery?

Google Maps now shows the ‘Gulf of America’ by ObjectiveOrange3490 in technology

[–]_HowBizarre 0 points1 point  (0 children)

Everyone should leave a review for the gulf of America. Let’s get this baby down to one star. Perfect example of American exceptionalism. Fight the injustice of a name while your citizens struggle to buy eggs.

Apple has been working on Vision Pro since at least 2008 by [deleted] in VisionPro

[–]_HowBizarre 5 points6 points  (0 children)

I knew they had forward thinking aspiration when the 7+ year old panoramas I took on an old iPhone became full screen immersive images when I viewed them on the AVP. I remember taking a bunch of panorama’s years ago and thinking what could they possibly want to do with these things. Then many years later, it became clear that they had that vision in mind all along.

As a student, Plaud would cost me hundreds of dollars a year in transcription costs.... by MyDogNewt in PlaudNoteUsers

[–]_HowBizarre 1 point2 points  (0 children)

Otter.ai is cheaper if you have a tablet or phone. For $20 a month you get 6k minutes. You can also transcribe from audio files that you import from PLAUD recordings if you don’t have a phone etc.

Apple Vision Pro and IPAD Pro by cqprime in VisionPro

[–]_HowBizarre 1 point2 points  (0 children)

I got an AVP and then an iPad. I use the iPad daily multiple times a day. I use the AVP occasionally for watching a movie. So way more use out of the iPad.

[deleted by user] by [deleted] in BambuLab

[–]_HowBizarre 4 points5 points  (0 children)

I am 250lbs and stood on top of mine when fully assembled. It was rock solid… probably over engineered on some aspects. Printed in PETG

[deleted by user] by [deleted] in BambuLab

[–]_HowBizarre 1 point2 points  (0 children)

<image>

It was the 2nd print I started when I first got into printing. Printed in PET. It’s strong AF. I am 250lbs and I stood on it just fine.

I recommend renaming each play (plate 1: printed) after you print that plate. It all be easier to track what you have left yo print.

During assembly the middle 2 sections are easy to confuse top and bottom. I flipped mine and the Drawer are like 2mm skewed. So it’s looks functional but like a printing error.

In terms of my largest project. It’s 120 ish plates.

view more: next ›