question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

How to resolve INCOMPATIBLE_EXTENSIONS error

See original GitHub issue

✅ Prerequisites

  • [ * ] Did you perform a cursory search of open issues? Is this question already asked elsewhere?
  • [ * ] Are you reporting to the correct repository (magic-sdk)?

❓ Question

I’m using magic-sdk 4.4.2 and @magic-ext/oauth 0.9.0. When trying loginWithRedirect as described here, I’,m receiving this error:

Uncaught Error: Magic SDK Error: [INCOMPATIBLE_EXTENSIONS] Some extensions are incompatible with `magic-sdk@4.4.2`:
  - Extension `oauth` supports version(s) `>=2.4.6`
    at new MagicSDKError (sdk-exceptions.js:17)
    at Object.exports.createIncompatibleExtensionsError (sdk-exceptions.js:138)
    at SDKBase.prepareExtensions (sdk.js:83)
    at new SDKBase (sdk.js:107)

I’ve tried to downgrade to magic-sdk 4.0.0 and oauth extension version to 0.7.0 (got the instructions from support), but id did not resolve the issue. I’ve also tried other versions.

🌎 Environment

Software Version(s)
magic-sdk 4.4.2
Browser Brave Version 1.26.74 Chromium: 91.0.4472.124 (Official Build) (64-bit)
yarn v1.21.1
Operating System Ubuntu 18.04.5 LTS

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
smithkicommented, Sep 14, 2021

Please give this a try with magic-sdk@6.0.1 and let me know how it works for you. If the issue remains unresolved please feel free to ping this thread and I’ll re-open the issue.

1reaction
smithkicommented, Sep 14, 2021

Took a deep dive into this issue and I believe it’s related to an old cyclic dependency within the semver package. Apparently there’s a known issue with bundling semver using Rollup that creates an unexpected behavior where semver.satisfies returns false always.

Related issues:

We are in the midst of a refactor that will bundle all Magic SDK dependencies together before publishing to NPM. I have run into this bug myself while implementing that change. I will try to resolve it for you from our side and ping this issue when the fix goes out (should be in v6.0.0).

Read more comments on GitHub >

github_iconTop Results From Across the Web

How to Solve the 'Control Panel Extension is Incompatible ...
Method 1: Updating the Synaptics driver via Device Manager​​ Since the number one cause that will cause this 'Control panel extension is  ......
Read more >
Control Panel Extension is Incompatible with Driver Version
Apply the solutions in this post to effectively fix the Control Panel Extension is Incompatible with Driver Version error on Windows 11/10.
Read more >
Solved: Control Panel Extension is Incompatible with Driver ...
5) Reboot your Windows and check to see if the problem disappears. Welcome! What's going on with your computer?
Read more >
How to fix "The extension is incompatible with the targeted ...
The problem is: I keep getting (when attempting to update on the marketplace). The extension is incompatible with the targeted version of Visual ......
Read more >
Fix: Control Panel Extension Is Incompatible with Driver Version
Method 1: Update the Synaptics Driver via Device Manager​​ As the error “Windows 10 Control Panel Extension is Incompatible with Driver Version” ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found