Sudden '3rd party library that is not supported' warning, not using anything AFAIK #27924
-
I suddenly started to see this message.
I understand what it saying but i don't understand why i'm affected. I'm running a cypress test in a Azure Devops Pipeline, i don't record anything anywhere. It seems like Azure Devops however is doing some kind of log parsing and displaying some info about what tests failed and so on, i never use it though. Can it be this that are causing this? And in that case how can i disable it? Do i have to downgrade to version 12 until this is resolved? Update: I did a downgrade now and that seemed to work. Still do not want to be stuck with an old version though. Br, Ola |
Beta Was this translation helpful? Give feedback.
Replies: 10 comments 19 replies
-
@olaj Could you run Cypress in debug mode mode where the error is occurring and print the entire set of logs here? |
Beta Was this translation helpful? Give feedback.
-
Same issue here with Github Action and Cypress 13.2.0 and 13.0.0 (but not 12.17.4). Here is my log:
|
Beta Was this translation helpful? Give feedback.
-
Wish we could see which packages are not supported by Cypress |
Beta Was this translation helpful? Give feedback.
-
I'm also running into this error message in GitHub actions w/Cypress 13.3. The error did not happen in Cypress 12.17.4. I'm running two different Cypress jobs in the same workflow, one runs successfully and the other fails with this message. Both jobs use the same package.json, so my thought is that this error message is likely a red herring. The failing job uses the cypress-repeat plugin. This error does not reproduce locally, it appears to be isolated to CI. |
Beta Was this translation helpful? Give feedback.
-
We're also running into this issue on Cypress 13.3 and we've not included anything in our config that didn't already work in Cypress 13.2. |
Beta Was this translation helpful? Give feedback.
-
Happened to me too when moving from 12.17.4 to 13... https://gitlab.com/txominsirera/dog-trainer-pwa/-/jobs/5207175700 this one is breaking This is the last commit https://gitlab.com/txominsirera/dog-trainer-pwa/-/merge_requests/53/diffs?commit_id=2b4045e394ef71f51081f55a77fae7fe0bb8348e#a829ed6336deb68f9874e5da490e1ec440b0e9b7 |
Beta Was this translation helpful? Give feedback.
-
I have the same error but in github actions. |
Beta Was this translation helpful? Give feedback.
-
We've identified a situation where blocking is occuring when it should not be and are working to fix it as soon as possible. I'll update once we have that fix out. |
Beta Was this translation helpful? Give feedback.
-
If you were not using a third party library and were encountering an error blocking usage of Cypress on 13.x versions, this issue should be resolved. You may need to clear your cache to get the updated fix. Some CI environments have unique caching strategies, so please read your CI providers docs to ensure the cache is cleared. If you're still encountering an error that you believe is an error on our part, after ensuring your cache was cleared, please open a new issue so we can investigate. |
Beta Was this translation helpful? Give feedback.
-
May not be the case for everyone experiencing this issue, but I wanted to share how we resolved it in case anyone else came across this discussion. Like the others we were only seeing this issue in CICD, tests ran fine locally even when adding the record flag. This issue surfaced for us when upgrading from Cypress 9.1.0 to Cypress 13.6.4. Our project is in an NX monorepo and we had also just gone through upgrades for NX and Node. As it relates to Cypress, and possibly this issue, we switched from the In our GitHub action yml, we ran the Cypress tests with this command, which had been working prior to the upgrades:
I ended up adding the
Notice it has
I then re-ran the workflow and that args block correctly showed I'm guessing others here might have a different root issue, but we're all seeing the 3rd Party Library error incorrectly being triggered and masking the real error in the logs. |
Beta Was this translation helpful? Give feedback.
If you were not using a third party library and were encountering an error blocking usage of Cypress on 13.x versions, this issue should be resolved.
You may need to clear your cache to get the updated fix. Some CI environments have unique caching strategies, so please read your CI providers docs to ensure the cache is cleared.
If you're still encountering an error that you believe is an error on our part, after ensuring your cache was cleared, please open a new issue so we can investigate.