Facebook Mobile URL with Shields UP

Troubleshooting technical issues is much easier when both the user and support agent practice clear communication. For this reason, we have provided the template below for you to fill out with information about your issue. Please provide as much detail as possible so we can most efficiently resolve your problem.


Description of the issue:
As of the past 24 hrs, when I use Brave with Shields Up on the mobile URL for Facebook m.facebook.com, I am unable to reply or comment on many (possibly all) posts from my friends list. I am able to reply and comment on some public posts.
I’m able to post new topics on friend’s feeds but can’t reply or comment thereafter.

When I take Shields Down, I’m able to post and reply normally.
When I switch to desktop setting all works well with Shields Up.

How can this issue be reproduced?

  1. Run Brave on my phone, Shields Up.
  2. Open URL m.facebook.com
  3. Find a friend’s post, “Comment As” window is not rendered.
  4. Attempt a “Reply” to a post, screen dims but no Reply field appears.
  5. Attempt to edit/delete a prior Reply, screen dims but no action is possible.
  6. Take Shields Down, all works well.
  7. Switch to Desktop mode, all works well.

Expected result:
Normal behavior for post Replies and Comments.

Brave Version( check About Brave):
1.74.48
Mobile Device details
Pixel 7 phone, Android 15, Build AP4A.250105.002.
Additional Information:
Use other browser (Chrome) all works well with both mobile and regular URL.
Unable to emulate Pixel 7 on desktop version of Brave pointed at mobile URL. The session redirects to desktop version. Have been unable to prevent that.

4 Likes

It’s not just you. Mine started doing this as well.

2 Likes

Same issue, Samsung Galaxy S23, OneUI 6.1
Brave 1.74.48, Chromium 132.0.6834.83
Android 14; Build/UP1A.231005.007

1 Like

Thanks for sharing all the details—it’s super helpful in figuring out what’s going on. From what you’ve described, it sounds like Brave’s Shields are blocking some scripts or features that Facebook’s mobile site needs to let you comment and reply properly. Since everything works fine when Shields are down or when using Desktop Mode, it seems specific to how Shields interact with the mobile version of Facebook.

One thing you can try is tweaking the Shields settings specifically for m.facebook.com. While on the site, tap the Brave icon in the address bar and see if turning off specific protections, like blocking trackers or scripts, changes anything. That might pinpoint what’s causing the issue.

It’s also a good idea to clear your cache and cookies for Facebook within Brave. Sometimes cached data can cause unexpected issues like this. If you do that and it still doesn’t work, you could try toggling off “Prevent cross-site tracking” just for Facebook and checking if that resolves the issue.

If none of this works, it’s worth reporting the problem directly to Brave’s support team so they can investigate. You can do this through the app under Help & Support. For now, using Chrome or Desktop Mode might be your best workaround while waiting for a fix.

Hi. I did report it via the app.
For now I put shields down if i want to interact w/ FB, which is easy enough to do.

Turning off “block trackers & ads” allows posting again.

Disabling the features in brave that inspired me to use brave means I should no longer use brave.

Stupid suggestion.

Thanks all for reporting. When you have a moment, can you please update to 1.74.50 and confirm that the issue persists? I’ve opened an issue for the team to review https://github.com/brave/brave-browser/issues/43580.

Problem still persists.

Brave 1.74.50, Chromium 132.0.6834.111
Android 14; Build/UP1A.231005.007

Problem persists plus now three dot menu or share menu within Facebook do not open at all.

Should be fixed now, can anyone confirm (with shields=UP)? @Techviator @roosclan @Hazelip @CJV

1 Like

Yes, has been working for a bit; it seems removing the “get the app” banner is what broke it. It is working now, but the banner is back.

Yeah correct, seems FB changed the div elements.