app disabled "Platform Term 7.e.i.1 - Timely response to our requests" despite no late responses
67

In case some from Facebook sees this... App ID: 1513726288954099

We received notification of restrictions due to "Platform Term 7.e.i.1 - Timely response to our requests".

See screenshot; the message lists our several resolved app review cases and an additional request for information with 14 days remaining to respond. We have responded to app review requests regularly and repeatedly, each time with a successful resolution, as shown by the screenshot.

https://developers.facebook.com/appeal also states "None of your apps are restricted."

Chris
Gefragt vor etwa 4 Monaten
Brett

Having the exact same problem along with no apps showing up in the appeal link.

Really struggling with this today as there doesn't seem to be any actions that we can take on our end and we haven't been able to hear back from anyone at Meta.

11. Juni um 11:37
Michael

In case someone from facebook sees this as well: App ID (498081203707521) We are experience the exact same thing with our app. We have a violation that we got an extensions for but for whatever reason we just lost the ability for our app to access the facebook API even though we have 42 days to resolve it.

11. Juni um 12:03
Graeme

We keep responding to a login broken violation (even though when we use the same test creds it works) we have replied multuple times now we have just been pimged with this violation aswell

No customer support so way to appeal (as apparently no apps are restricted even though they are) the whole plaform seems to be a complete mess right now and no way to report bugs for these issues weither as the categories are missing

11. Juni um 13:14
Krystian

Hi! Same here happened to our app (App ID: 723262884730399) We got the violation which was resolved four days ago. Today, we got the email about the same issue you are facing. It is impossible to resubmit the form about previous violation, since it is resolved.

11. Juni um 13:32
Lee

We have the exact same issue: https://developers.facebook.com/community/threads/1577285509493389/.

11. Juni um 13:59
Avi

Same here

11. Juni um 22:06
Henning

Same for us, App ID: 2521847297962966

11. Juni um 22:48
Henning

Help out to get metas attention by creating bugs here https://developers.facebook.com/support/bugs/create/

Use this tag to be able to create a bug report "Developer Tools, App Dashboard, Basic/Advanced Settings"

12. Juni um 00:31
Craig

Same. Asking to resolve already resolved violations. Screenshot: https://imgur.com/a/fj1d5SK

12. Juni um 01:58
Lars

Read the information again, it's not asking you to resolve already resolved issues, because it lists "resolved" next to it. The notice says you did not respond in time to one of these requests.

12. Juni um 02:32
Florian

We're facing the same issue...

12. Juni um 02:45
Krystian

@Lars, we are facing the same situation as Chris (and many others). We received a violation warning on May 23 with 1 month to reply, until June 24. We replied to this violation and on June 7 we received a message saying "Violation resolved". There were no other messages/violation/alerts received after that, yet, yesterday, we got the restriction as Chris. Even if we or Chris did not respond in time, there is no way to push the process forward and appeal/reply to the restriction.

12. Juni um 02:45
Chris

@Lars Look at the screenshot again. Each item in the "open violations listed below" is either resolved (all but one) or has two weeks left to respond to.

12. Juni um 03:27
Movable

It's both a relief to know that this isn't only happening to us but also incredibly frustrating that something like this can happen. We resolved our violations as soon as we got the initial email on May 23rd and our application was still restricted with no way of appealing. We now have the same violation for 7.e.i.1 with no way of resolving as all other violations were resolved too.

12. Juni um 07:40
Lars

@Chris I was referring to Craig’s screenshot, which seems to be a different issue than yours

12. Juni um 07:41
Chris

@Lars It looks very much like the same issue; the only difference is we had one pending with a (future!) due date; Craig didn't even have one of those. Something's broken.

12. Juni um 07:50
Will

Yes, we're having the same issue. (APP ID 1587138971603645)

12. Juni um 16:30
David

Yes, we are also experiencing exactly the same issue with our app being suddenly restricted on June 12th even though we have resolved all our violations. APP ID: 439906197109302

12. Juni um 20:03
Loek

Same here App Id 965579890627932

13. Juni um 03:22
Totte

We are experiencing the same. We had 14 days left until the deadline when this was enforced earlier this week.

13. Juni um 05:56
Chris

Note to @Facebook; this is currently the #2 most upvoted thread ever in these forums after only two days. Y'all have an issue going on.

13. Juni um 14:42
On

Facing the same issue. App is restricted 1824222801089869

13. Juni um 21:42
Chris

We remain restricted this morning despite a successful resolution of our not-yet-due review clarification. The notification continues to tell us we must respond to the (all resolved) items. https://imgur.com/a/3UiouSU

14. Juni um 04:22
Chris

Same issue here: App ID: 326873532312104

17. Juni um 09:22
Safal

Same with us

18. Juni um 02:02
Filip

Same here: App ID: 568410092012196

18. Juni um 06:29
Martin

Same issue for us, App ID: 205360614747660

20. Juni um 03:43
Gari
Same issue (wrongfully restricted for 2 weeks now) App ID
752078144824356
23. Juni um 04:01
Cassie
Same issue (wrongfully restricted for 3 weeks now) App ID
332203686891731
23. Juni um 22:57
Lee

We're finally getting somewhere are finding and using the direct support channel via our Business. https://business.facebook.com/direct-support/. I'm getting prompt replies here, and helpful information about what needs to be done.

26. Juni um 16:53
Chris

@Lee We did not have luck with business support; I spent two hours on a screen share with a rep going through the "appeal? file a bug? post in dev forum?" loop with them. Escalation to a supervisor was similarly fruitless.

What are they saying you need to do?

26. Juni um 17:58
Chris

Our app came back into live mode this morning. Hoping it's a fix across the board; anyone else see the same?

1. Juli um 06:12
Krystian

We got our app restored on Friday's evening!

1. Juli um 09:55
Bett

@Krystian what did you do for them to restore it?

3. Juli um 06:32
Krystian

@Bett, to be honest, we didn't do much. We tried multiple methods to reach someone at Meta to remove the restriction. We created a new app and submitted it for review, including information about the restriction on our current app. The new app was approved, but there were no feedback about current restriction.

Direct Support could have been more helpful, as @Chris mentioned. They didn't provide any solution, but we learned that only Meta Business Partners can submit bugs.

After 18 days, the restriction was unexpectedly removed. It seems you just have to wait for someone to review your app to lift the restriction. Ensure that the testing instructions under App settings are clear and functioning correctly. If they are incorrect, you will probably receive another violation and have to wait for another evaluation.

3. Juli um 07:24
Ausgewählte Antwort
1

Hello Team,

App ID: 432805290684776

After we have finished all required actions, the app is still in restricted mode. This application is created for differently abled persons and domain of the application is Public Health. Moreover this app is created for free usage. App can't be in restricted for these many days as users can't speak to call centre team and specifically designed to cater deaf, speech impaired and hard hearing people. Kindly allow the app so that emergency cases will be placed by the users. Request you to let us know if additional information required on the same.

12. Juli um 03:12
Ehm
Ehm

The app is still in restricted access. Would you kindly take the app out of restricted access? Disabled people use our app to get assistance in (medical, police, fire) emergencies. Users are unable to access the app since it is restricted.

14. Juli um 22:56
Ehm

Any update on the app restriction, we have finished all required actions. Kindly provide update as this is impacting the application which is in live environment.

15. Juli um 06:49
Ehm

Hello Team, would you kindly take the app out of restricted mode? The app has been restricted for more than a month, which has affected users' ability to utilize it in emergency circumstances (police, fire, medical).

16. Juli um 00:56
Ehm

After we have finished all required actions, the app is still in restricted mode. The app has been restricted for more than a month, which has affected users' ability to utilize it in emergency circumstances (police, fire, medical).

16. Juli um 07:20
Ehm

Any developments on the app restriction? Please provide an update, as this is having an effect on the live application.

17. Juli um 00:26
Ehm

Nothing has changed on our end; the restriction is still in place. App was in restricted mode for about a month. I respectfully inquire with you; Did you take any particular action to get the restriction removed?

19. Juli um 05:51
Mario

we are in the same boat

22. Juli um 01:33
1

Hello Team,

App ID: 432805290684776

The app is still in the "Restrictions" state despite having completed the necessary activities.

Resolved the open violations indicated below in order to get the app live.

Resolve violation, Resolved Jul 2, 2024 Resolve violation, Resolved Jul 15, 2024 Resolve violation, Resolved Jul 11, 2024 Resolve violation, Resolved Jun 17, 2024 Resolve violation, Resolved Jul 19, 2024

Please take down the app's limitations so that people with disabilities can utilise it in emergency (Fire, Medical, Accident) situations.

21. Juli um 22:55
Ehm
Mario

was your restriction finally lifted?

24. Juli um 23:27
Mario

We have a similar problem. There are new violations from time to time, which are solved by sending the same information again. However, Platform Term 7.e.i.1 remains in place and the app is still restricted.

To restore the app, respond to the open violations listed below. Resolve violation, Resolved Jun 13, 2024 Resolve violation, Resolved Jul 24, 2024 Resolve violation, Resolved Jun 24, 2024 Resolve violation, Resolved Jul 16, 2024

24. Juli um 23:30
Ehm

Not yet, still app in restrictions state.

29. Juli um 06:12
Mario

same here

30. Juli um 08:08
1

Same here please help!! .. App Id: 265388275487276

1. Oktober um 10:59
Mina
2

Same issue here, app ID 333107034572374

3. Juli um 12:52
Érij Maherzia
2

Hello Facebook Team,

App ID: 432805290684776

Resolved below required actions, the app remains in the "Restrictions" state.

To restore the app, respond to the open violations listed below. Resolve violation, Resolved Jul 2, 2024 Resolve violation, Resolved Jun 17, 2024

Would you kindly remove the app's restrictions so that disable users can use the app.

7. Juli um 23:39
Ehm
Ehm

This application is created for differently abled persons and domain of the application is Public Health. Moreover this app is created for free usage. App can't be in restricted for these many days as users can't speak to call centre team and specifically designed to cater deaf, speech impaired and hard hearing people. Kindly allow the app so that emergency cases will be placed by the users. Request you to let us know if additional information required on the same.

8. Juli um 00:23
Ehm

Any update on the app restriction as this request is pending from almost 1 month and no update from community group. Kindly provide update as this is impacting the application which is in live environment.

8. Juli um 05:08
Ehm

After we have finished all required actions, the app is still in restricted mode. Please remove the app's restrictions so that disabled users can use it in an emergency.

11. Juli um 07:19
2

For us the restrictions are finally lifted! We received a new violation request, so we could resend our answer. It turned out, that the reviewers searched for a Facebook integration. But we only have an Instagram integration in our App...

22. Juli um 01:14
Florian
3

I've given up on Meta at this point. We've had another violation resolved, yet we're still restricted with no way around it.

20. Juni um 13:20
Lee
3

Same here APP ID: 1207926246269332

1. Juli um 07:20
Sarunas
Chris

When did your app get restricted? Just today?

1. Juli um 07:43
3

Finally After 17Days our restriction removed.Hope this issue resolve for all soon.

1. Juli um 09:25
On
Krystian

Same for us, the restriction has been removed. It took 18 days. Fingers crossed, it will be soon sorted out for everyone else still having this issue!

1. Juli um 09:57
3

Same here. APP ID: 266263811710369

2. Juli um 06:35
Ľuboš
3

Same here. APP ID:143725081100953

2. Juli um 19:58
呂夏天
3

same here. App ID: 1019655702248344

2. Juli um 20:24
Bevis
3

Thank you! I was struggling to find any answers on this and knew we couldn't be the only one with this exact same issue.

App ID : 517812196504983

3. Juli um 06:43
IPr
4

We've just had one of our "violations" re-opened which has allowed me to resubmit the required information so perhaps we're finally getting somewhere. Our app has been restricted since June 11, and we've just had movement as of June 18

17. Juni um 13:36
Lee
Chris

We resolved one (that still had 13 days "until restrictions" at the time) and received the usual all-clear email from the reviewers.

Unfortunately, the app remains restricted with the unanswerable "timely responses" violation several days later.

The main app dashboard indicates that "timely responses" violation is due in 2025, too.

17. Juni um 14:18
Krystian

A similar thing happened on our end. Initially, we received a regular violation, "Broken Facebook Login," which was resolved on June 7. On June 11, we received a "Timely response" restriction. Today, we received the same violation about "Broken Facebook Login" so we could reply. We are currently waiting for the results.

@Lee, kindly update this post if you receive any response or if the "Timely response" restriction will be removed after the review.

18. Juni um 00:26
Krystian

Update: we got a favorable response to the new violation received today (Broken Facebook Login). It was resolved, but the app is still restricted. So the review didn't resolve anything for us:/

18. Juni um 05:26
Florian

Same here. We received a new "old" violation today. It was resolved but the app is still restricted...

18. Juni um 06:59
Katelyn

Our app had the same issue, we resolved the violation on 6/13 and then just had the restriction lifted today. Sounds like they have a massive backlog, hopefully they get to everyone soon!

18. Juni um 07:32
Krystian

Thank you for the update, @Katelyn! We also noticed one thing in the restriction text that wasn't there before (compared to the screenshots we have):

If you are receiving this violation and have already responded to all other violations, your responses are in process.

The information is not very visible at first glance. A better UX would be adding "In review" messages when you have resolved violations instead of just displaying a "Restricted" label.

18. Juni um 07:48
Movable

This happened to us also. Our resolved violation for 7.a. was re-opened just after we had all of the restrictions lifted for 7.e.i.1.

We resubmitted the instructions that we always give and it eventually got resolved a few hrs later.

One thing to call out, for anyone else that deals with 7.a., is that there's a setting all the way on the bottom of Basic App Settings, that lets you submit your app review instructions. I think that this is the reason we kept getting 7.a. violations, even though we've submitted review instructions before in the past via these violation resolutions. My guess is that Meta's app review process doesn't transfer response submissions onto the app's settings, and their reviewers don't check previous submissions for instructions either.

18. Juni um 08:56
Lee

We had a "violation" resolved, and yet we're still restricted. Meta is becoming a joke by this point

18. Juni um 15:07
Krystian

In our case, the app went from Live to Development mode. Only the test users and people with roles can query the API. The approved permissions have the "Advanced access granted" status, so we hope that once the restriction is removed, the review for advanced access will not be necessary.

21. Juni um 02:37
Lee

Except the restriction won't ever be removed. We're going down the track of creating an entire new app in Facebook

23. Juni um 15:38
4

Same for App ID: 432805290684776

19. Juni um 23:00
Ehm
Ehm

The app continues to have the same problem. Would you kindly take the app out of restricted mode? Disabled people use our app to get assistance in (medical, police, fire) emergencies. Users are unable to access the app since it is restricted.

23. Juni um 23:57
Ehm

I hope that the Meta team has examined our posts. Due to restrictions, disabled people cannot utilize apps in emergency (medical, fire, and accident) situations. Would you kindly assist us in resolving about this issue?

26. Juni um 00:51
Ehm

After resolved all required actions (7.a & 6.1), the app's status is still restricted. Would you kindly remove the app's restrictions? So users with disabilities can utilize the app.

2. Juli um 22:04
Ehm

Hello Facebook Team,

Resolved below required actions, the app remains in the "Restrictions" state.

To restore the app, respond to the open violations listed below. Resolve violation, Resolved Jul 2, 2024 Resolve violation, Resolved Jun 17, 2024

Would you kindly remove the app's restrictions so that disable users can use it.

3. Juli um 22:26
4

Same issue: App ID: 151075517212838

26. Juni um 00:18
Hou Zhi
4

We have the same issue ourAPP ID : 2753260454985507

27. Juni um 22:38
Varun
4

Same here... App ID: 2175533829266414

1. Juli um 01:57
Teodora
4

It got fixed! The violation message just vanished automatically today and my app is back live

15. Juni um 01:31
Avi
Chris

Ours has not yet. Hoping it's some backlogged process they're working through.

16. Juni um 10:43
Nichole

Ours has not resolved yet either. And Meta Direct Support has been zero help.

16. Juni um 18:02
Florian

Ours is still restricted. Really frustrating. @Avi: Have you done anything other than wait and hope for the best?

17. Juni um 00:05
Krystian

It's the same thing on our end - the restriction is still in place. It would be awesome to get some insights from someone whose restriction was removed, just like @Florian asked - how long was the app restricted? - did you take any particular actions to remove the restriction? - were you notified via email that the restriction is no longer available, or did you visit your app settings and see that it is no longer restricted?

17. Juni um 02:05
Craig

Assuming you are talking about this Timely Response restriction. My app was restricted for about 3 days. I messed around with business settings to try and fix it, but really I didn't do anything. I was notified about the restriction, but not of its removal, it just magically resolved itself.

17. Juni um 16:56
Katelyn

@craig any specifics on what you did with the business settings? We've been considering changing our logo or name to trigger a review or something but also don't want to mess anything up. We are going on day 7 and really want to resolve this issue for our users.

17. Juni um 17:25
Chris

@Katelyn We attempted a logo change; it came back as approved in under 10 minutes.

I did include a big all caps note about the bug asking for escalation to the team... but that's a bit of a hail-mary sort of thing.

18. Juni um 07:24
Chris

(and to be clear, the approved new logo didn't fix the problem)

18. Juni um 07:24
4

Same here app id: 457100969311975

17. Juni um 02:31
村野弘幸
4

same for us app id: 705159133212396. We've been waiting more 14 days.

17. Juni um 09:06
Mark
5

We received a new violation today, We resolved that violation but the app is still restricted. We are hoping it might take some time to remove the restrictions.

20. Juni um 04:37
On
5

Same here!

APP ID: 1667164766917533

21. Juni um 04:14
Rafael
5

Same here app id: 506589843384401

21. Juni um 07:58
Gad
5

My app got restricted even before the deadline given to resolve the issue. We resolved all the issues and its more that 3 weeks now that the app is in restricted state. Not able to connect with meta support. The link for developer support in the page seems to be broken.

My App ID: 795682684261255

23. Juni um 10:10
Ghanshyam
Ghanshyam

Any update on this? Its been months now. Our customers are facing a lot of issues because of this.

9. Juli um 22:41
Ghanshyam

Anyone able to resolve this issue?

12. Juli um 01:08
Ghanshyam

My app does not appear in the "/appeal" page so I have no way to contact the reviewer and get my app restored I also tryed to respond in the violation notification but when I submit my response, I just receive an error

12. Juli um 01:10
5

same here. we've been wasting for almost 3 weeks app id : 1665716787017709

23. Juni um 18:20
고준성
5

same here. tried everything, contacted fb so many times. nothing works.

14. Juni um 09:08
Komaeda
5

Same here App ID: 535765177821555

14. Juni um 15:22
Jackson
6

It's fixed! The "Timely response" violation has magically been resolved, and my app is no longer restricted. Yay!

13. Juni um 17:33
Craig
Chris

We're still in the stuck state at the moment. Got a "violation resolved" notice for the thing that wqas due in two weeks that we responded to, but the "timely" one is still in effect.

Hoping it's just a fix rolling out.

13. Juni um 18:16
Nichole

We're still in a restricted state.

13. Juni um 18:16
Avi

My app is still stuck

13. Juni um 22:19
Mario

our app is still restricted

13. Juni um 22:45
Florian

still restricted

14. Juni um 00:34
Krystian

We are still restricted:/

14. Juni um 00:39
Loek

Stuck

14. Juni um 05:44
David

Got a new violation message saying our integration is broken and that they will begin restrictions in a month's time. But it is broken because the app is restricted so I'm not sure what is going on internally but something seems really screwed up.

14. Juni um 05:50
Austin

We are still restricted despite no open action items - every violation is in a resolved state. This is definitely not fixed for everyone

14. Juni um 05:59
Mario

still restricted, over a month now ...

22. Juli um 23:51
6

@Facebook - will you be compensating all of the developers impacted by this issue? We're going on 6 days now and this is still not fixed. Customers are asking for compensation.

17. Juni um 05:42
Daniel
Lars

Compensation for a paid service you offer that relies on a free platform? Good luck with that.

17. Juni um 05:47
7

It is unbelivable, my app has been restricted for almost 2 weeks now and I have aboslutely no ongoing violation, it does not appear in the "/appeal" page, I can't contact anybody to help me

I don't know if people from Meta are reading posts here anyway.

Our application was flagged "In violation" during the periodical review (just because the reviewer could not find the "Facebook Login" button). We were supposed to have a few days to respond before our app was restricted, but even before the end of the delay it got restricted !!! Of course we solved the violation but our app is still restricted and I have a message asking me to resolve violation, but the violations are already resolved:

Extract from my "Required Actions" notification :

-- To restore the app, respond to the open violations listed below. Resolve violation, Resolved May 28, 2024 Resolve violation, Resolved Jun 4, 2024 Resolve violation, Resolved Jun 14, 2024 The violations in the list above will be resolved after you submit the required information and our reviewers have been able to confirm the issues are addressed. If you are receiving this violation and have already responded to all other violations, your responses are in process.

After our reviewers complete their review of the app, this violation will be resolved, and the app will be automatically restored.

My app does not appear in the "/appeal" page so I have no way to contact the reviewer and get my app restored I also tryed to respond in the violation notification but when I submit my response, I just receive an error (I guess because it is resolved, so we can not respond anymore)

23. Juni um 04:10
Gari
7

We were in the same boat but it just resolved itself a couple minutes ago.

13. Juni um 17:15
Justin
Nichole

How long were you in a restricted state?

13. Juni um 17:20
Craig

Same. All working again.

13. Juni um 17:34
9

Same here

13. Juni um 23:03
Thomas
10

Same issue with my app currently restricted: App ID: 906268027223497

13. Juni um 11:48
Devon
10

Same here.

13. Juni um 22:43
Charlie
11

Has anyone gotten a resolution on this? We're going over 48 hours with our app being restricted with this issue.

13. Juni um 16:44
Nichole
Craig

Nothing here. The whole thing is strange. Facebook contacted me about the previous violations saying they didn't have any login to test. I had to give them the user and password to my test account. This whole thing seems mismanaged.

13. Juni um 17:07
Nichole

Same here. I have an open Direct Support ticket but they just keep copying and pasting the same platform policy information with no real answers.

13. Juni um 17:19
12

Same here.

12. Juni um 22:42
Steve
12

Same here app id: 965579890627932

13. Juni um 03:19
Loek
13

Same issue, app currently restricted, ID: 262469144522118

13. Juni um 08:14
Mario
Kyle

I've resolved both violations...sitting there on my app dashboard as resolved with the big red banner of app restriction makes me so livid!

16. Juli um 23:21
21

Facing same issue here

12. Juni um 02:15
Saurabh
Kyle

This is so discouraging

16. Juli um 23:20
Kyle

Same issue here

16. Juli um 23:20
21

Same here.

12. Juni um 07:35
Movable
22

We're experiencing the same thing with our app.

12. Juni um 16:29
Newton
27

i am having the same exact issue with my app

11. Juni um 12:49
Ahmed
Rafael

still having

21. Juni um 04:55
Kyle

I'm having the SAME EXACT ISSUE!!!!!

16. Juli um 23:19
Kyle

This is crazy and most disheartening

16. Juli um 23:20