New Participant

Question

App Review final submit blocked by hidden fblogin-web-1 validation label

Forum|Forum|4 months ago
June 6, 2026
7 replies
425 views

Meta App Review final submission for our app is blocked by a hidden/internal validation label. All visible App Review sections are complete/green, but final Submit returns:

Some sections are incomplete

question labels are invalid: fblogin-web-1

App: Hermes Bot

App ID: 2389952421516474

Business ID: 1114463873276065

Submission ID: 2407995389712177

Expected behavior:

- The submission should submit successfully because every visible required section is complete, or

- The UI should render the missing question/field that maps to fblogin-web-1 so it can be completed.

Actual behavior:

- The final submit confirmation modal accepts the acknowledgement checkbox.

- After clicking the modal Submit button, the page returns the fblogin-web-1 validation error.

- No visible App Review section, Website platform testing instructions, Facebook Login for Business settings field, Facebook Login for Business configuration field, or Instagram setup field is visibly marked incomplete.

Troubleshooting already completed:

- Verified App Review checklist sections are complete/green: Verification, App settings, Allowed usage, Data handling, Reviewer instructions.

- Accepted the Instagram tester app invite for Hermes Bot-IG under the wheelsfeelsusa Instagram account.

- Checked/filled Website platform testing instructions.

- Checked Facebook Login for Business settings.

- Set and saved owned-site values: Valid OAuth Redirect URI https://wheelsfeels.com/, allowed domain wheelsfeels.com, deauthorize callback URL https://wheelsfeels.com/privacypolicy, data deletion request URL https://wheelsfeels.com/privacypolicy.

- Created/reviewed Facebook Login for Business configuration for the support workflow.

- Corrected configuration assets from Pages + Pixels to Pages + Instagram accounts.

- Checked Instagram business login/API setup and generated/validated tester authorization where visible.

- Retried final submission after each plausible fix. The same hidden fblogin-web-1 blocker persists.

Requested help:

Please advise the exact product/settings page and field that maps to fblogin-web-1, or escalate/fix the hidden validation state so the missing field is surfaced or the submission can proceed.

B

bikanerijaat00

New Participant

My account disable Ho Gaya hai

B

bikanerijaat00

New Participant

My account disable Ho Gaya galti se

muzammilyahia

Participant

Hi dmytroautomationwf,

This is a textbook Meta Dashboard UI validation bug, and it is incredibly frustrating. The platform backend is expecting a mandatory field entry mapped to the legacy or specific internal label fblogin-web-1 (typically associated with the classic Facebook Login Web Platform Component Setup), but the frontend UI fails to render the actual text field or checkbox for you to complete it.

Since your App Review checklist is fully green, you have two actionable developer workarounds to force-bypass or surface this hidden validation state:

1. The Console/Inspect Element Surface Trick

Sometimes the container holding fblogin-web-1 is rendered in the DOM but hidden via CSS (display: none or visibility: hidden).

- Open your Chrome DevTools (F12) or Brave Inspector on the final submission page.

- Go to the Console tab and search the DOM for that specific key by running:

document.querySelectorAll('[data-testid*="fblogin-web-1"], [name*="fblogin-web-1"], [id*="fblogin-web-1"]')

- If it returns an element node, change its style properties manually via the Elements tab to surface it, fill the required string, and click submit.

2. Platform Tear-down and Re-addition

If the DOM approach fails, the database mapping for your Submission ID (2407995389712177) is likely corrupted with a ghost dependency.

- Go back to your App Dashboard -> Settings -> Basic.

- Scroll down to your Platforms. If you have "Website" or "Facebook Login for Business" added, document your configuration details.

- Delete the platform entirely, save changes, refresh the browser, and then re-add the platform from scratch. This forced state-refresh usually overrides the ghost fblogin-web-1 requirement on the submission payload.

---

On a side note for any passing Community Manager:

It seems the automated systems and background endpoint validations across the Meta Developer ecosystem are triggering massive false-positives lately. While this developer is stuck on a hidden UI validation loop for the "Hermes Bot" app, my entire multi-platform production tools and integrated Graph API endpoints have been completely halted for two weeks now.

This occurred after a sudden automated security checkpoint locked my 2019 immaculate developer profile, failing to account for regional cellular infrastructure blackouts that forced my traffic through a Starlink satellite terminal (causing dynamic CGNAT IP roaming).

Whether it is a ghost fblogin-web-1 validation label blocking submissions, or an automated checkpoint locking live production integrations due to satellite routing—the internal developer support teams urgently need to step in and run human audits on these false-positives.

Hope one of the workarounds helps you push the code through!

Best regards,

KG

D

dmytroautomationwfAuthor

New Participant

Update: we double-checked this again and found one more place where fblogin-web-1 actually appears.

Per current Meta App Review submission flow, it is exposed under Reviewer instructions -> Website review as:

fblogin-web-1

Is Facebook Login integrated on this platform?

Yes / No

We tried both values and retried final Submit for Review after each attempt. The same validation error still appears:

Some sections are incomplete

To submit this form, you need to answer every required question. The following question labels are invalid: fblogin-web-1

Additional things we have now tried:

- Re-opened the full App Review flow and clicked through Verification, App settings, Allowed usage, Data handling, and Reviewer instructions to force autosave/current-schema refresh.

- Found the visible fblogin-web-1 question in Reviewer instructions.

- Selected Yes, returned to submission, confirmed the final submit modal, retried. Still blocked.

- Selected No, returned to submission, confirmed the final submit modal, retried. Still blocked.

- Previously also removed/re-added the Website platform, re-saved Site URL https://wheelsfeels.com/, Website testing instructions, App Domains, Privacy/Data Deletion URLs, Facebook Login for Business settings, and confirmed the configuration exists.

So this no longer looks like a field we simply cannot find. The field exists, but the final submit validator still rejects it after answering it. Is there any way to force-refresh/migrate the submission draft schema, clear the stored answer for fblogin-web-1, or have Meta/App Review engineering reset this hidden validation state for the app/submission? Any other workaround we should try?

muzammilyahia

Participant

Hi dmytroautomationwf,

Excellent find on locating the field. This confirms that the issue isn't a missing UI element, but a "Submission Schema Mismatch." Essentially, the final submit validator is checking a cached version of your draft that hasn't synchronized with the updates you made in the Reviewer Instructions.

Since the standard "Remove/Add Platform" didn't clear the ghost validation, you are likely facing a dependency loop where the backend thinks fblogin-web-1 is required because of a secondary setting elsewhere.

Here is the "Nuclear Option" to force a schema reset:

1. The Draft Deletion Trick:

Meta's submission flow often gets stuck if a draft is too old. If possible, try to cancel the current "Submission" entirely (not the app, just the review submission draft) and start a brand new submission from scratch. This forces the system to pull a fresh validation schema for your App ID.

2. Browser Session & Cache Hard-Reset:

Believe it or not, Meta's dashboard heavily uses local storage for draft states. Open an Incognito/Private window, log in, and try to change the fblogin-web-1 value and submit immediately. This ensures no old session tokens or cached validation states are interfering with the POST request.

3. The API Version Sync:

Check if your App is using an older Graph API version in "Settings -> Advanced." Sometimes, upgrading to the latest v20.0 (or current stable) forces the App Review module to update its required question set, potentially clearing the legacy fblogin-web-1 label.

---

On a side note regarding system-wide glitches:

It is becoming increasingly clear that Meta’s automated validators (both for App Review and Account Integrity) are currently out of sync with actual developer states. While you are battling a "Ghost Question" that won't validate despite being answered, my entire production environment remains crippled by a "Ghost Security Checkpoint" that ignored my manual Starlink/CGNAT network logs.

I have officially escalated my case through the Meta Verified support channel (Ticketed via Co-developer) and we are currently in a "Human Audit" phase with support staff. If your submission remains stuck, I strongly suggest referencing the "Systemic Validation Failure" to a human agent, as these automated loops are clearly failing to reflect real-time developer inputs lately.

Stay persistent—once a human engineer looks at that Sub ID (2407995389712177), they can manually "Force-Pass" that specific validation label.

Best regards,

KG

erivanjrbr20

New Participant

I cannot submit my app for App Review due to a bug. App ID: 1544866123670159 (Acelera Comentários).

Clicking "Submit for review" returns: "the following question labels are not valid: fblogin-web-1".

All visible App Review sections are complete and green. I'm requesting advanced access for

instagram_manage_messages and instagram_basic, plus public_profile renewal for Facebook Login

for Business. A valid OAuth redirect URI (https://comentarios.aceleraatacado.com/) is configured

and validated. There is no editable field with the "fblogin-web-1" label anywhere in the form.

The bug report tool also fails with "An error occurred while creating the bug report".

Please reset the submission draft schema for my app so I can submit. Thank you.

muzammilyahia

Participant

Hi erivanjrbr20,

First and most importantly: You posted this as a comment inside an existing thread. To get actual traction from the automated filters or senior technical members, you need to create a completely new, independent TOPIC. Comments on other people's posts rarely get audited by the engineering backend team here.

Regarding your specific error ("the following question labels are not valid: fblogin-web-1"):

This is a known, notorious backend validation bug on Meta's developer console where hidden schema fields (usually from outdated legacy forms or older Facebook Login versions) get stuck in the submission draft. Since you literally cannot see or edit "fblogin-web-1" anywhere on your green dashboard, no amount of frontend changes will fix it.

Here are a few technical workarounds you should try immediately while trying to bypass this block:

1. The API Submission Route: Instead of relying on the broken App Review UI dashboard, try fetching your app review status and initiating the submission directly via the Graph API Explorer or a script using the `/app/plugins` or `/app/review_submission` endpoints (if your current access token permissions allow it). Sometimes pushing the draft status programmatically bypasses the broken UI validator.

2. Creating a "Test App" Clone: Go to your App Dashboard, click on your app name dropdown, and select "Create Test App". This generates a clean clone of your app settings with a new App ID. Try replicating the setup there to see if the fresh schema clears the ghost "fblogin-web-1" label, allowing you to submit the test app instead.

3. The Bug Report Tool Bypassing: Since the standard Bug Report tool is also throwing an error, try accessing it via a completely clean browser session (Incognito mode, cache cleared, and ideally through a different admin account linked to your Meta Business Manager if you have one).

Move this over to a brand-new Topic thread immediately so the community can upvote it for visibility. Good luck!

Get Help

Sign up

Login with SSO

Login to the community

Login with SSO