-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Instagram blocking extension? #25
Comments
This issue is due to an internal error reported by the extension, which was fixed several versions ago. |
I have this with version 2.0.7 on Chrome. |
Thanks for the feedback, I apologize for the bug, this issue only occurs in chrome, I've been using Firefox lately so I didn't notice it. I've submitted a new version 2.0.8 for review, please wait for it to be approved. |
Thank you! |
Hi there, not sure if anyone has the same issue but today Instagram seems to be blocking access to individual profile pages with the extension on. Turning it off allows access to the profiles. The extension still works in the main feed at least, but that's the only page that can be navigated.
This is what I see on any profile page:
![cDkMovd 1](https://private-user-images.githubusercontent.com/54609347/318350530-ee4c95e7-af1e-4a25-bb61-076d27308db0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ2NTAwMzEsIm5iZiI6MTcyNDY0OTczMSwicGF0aCI6Ii81NDYwOTM0Ny8zMTgzNTA1MzAtZWU0Yzk1ZTctYWYxZS00YTI1LWJiNjEtMDc2ZDI3MzA4ZGIwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjYlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI2VDA1MjIxMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWI3MzY1OTc1ZmYxZGZkODlhNjNjYzcyMzMyZjU3NWZjNjc4YzAxYWY2MWNmODhiNjIyZjI0MDUwMzc4NTVhOTQmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.2oQNZba2hcfNws1ppCOtvtqL-bQjLL5zhEh0LTXRrWA)
Not sure if it needs to be updated?
The text was updated successfully, but these errors were encountered: