Execution Error “Unsafe Eval” about instagramunfollowers HOT 8 CLOSED

I have been using your code for a considerable period of time and must say that you are doing an outstanding job. However, this is the first time that I have encountered this error.

from instagramunfollowers.

I have been using your code for a considerable period of time and must say that you are doing an outstanding job. However, this is the first time that I have encountered this error.

Never tried this in ios... I dont know how js will perfom in this device. Can you give me the extension name? I have an iphone to test it.

from instagramunfollowers.

Extension name is Web Inspector. Thank you for your fast response. There’s hasn’t been any updates to it recently since a year ago. And it has been working perfectly.

https://apps.apple.com/eg/app/web-inspector/id1584825745

from instagramunfollowers.

I’m guessing “Unsafe-eval” is “Unsafe Evaluation” right? Could Instagram or Facebook be limiting access to their source files for security purposes too?

from instagramunfollowers.

Quick Update:
The code works when using a Web Inspector/Debug app separately, but not when using a Safari Extension. I think this is because of default Safari settings that limit access to source files. Could you check those settings?

Also, does the Safari Extension I linked previously work on your end? I tried other extensions, but they all gave me the same error message. That’s why I’m suggesting to check the default Safari settings.

App used: DebugAnywhere (worked)
Extension(s) tested: WebInspector, DebugAnywhere (failed)

from instagramunfollowers.

Please keep in mind that the code worked previously with any Safari Extension. This means that the issue is likely a recent change to Safari settings or a bug in the Safari Extensions (on Apple’s end). I don't think it's best to close this issue yet, as there is a chance that it can be resolved.

from instagramunfollowers.

Please keep in mind that the code worked previously with any Safari Extension. This means that the issue is likely a recent change to Safari settings or a bug in the Safari Extensions (on Apple’s end). I don't think it's best to close this issue yet, as there is a chance that it can be resolved.

Im not having to much time right now. But if i have some free space i will take a look.

from instagramunfollowers.

@theashraf15 I previously answered a different issue relating to Apple software, which can be seen here.

The gist is that we are mostly targeting Chormium based browsers and Firefox, and do not directly support other software.
We will usually try to provide assistance regardless, but in cases like these, where the issue seems to be caused by a very specific use-case (3rd party extension in this case), we might not be able to.

I would suggest just turning off the extension when running the script, if that works.
If not, try running it via a supported browser.

I will say that the error you provided seems to suggest a CSP issue.
But not sure what could be the reason for that.

from instagramunfollowers.