Runtime TypeError with CoreProvider context in Next.js 16

[LouisJackson]

Describe the bug
Runtime TypeError: "null is not an object (evaluating 't.context')" after library upgrade from 6.25 to 6.26 in Next.js project using Adyen Dropin. The error occurs in the CoreProvider component and appears to be related to React Context initialization.

To Reproduce
Steps to reproduce the behavior:

1. Upgrade Adyen Web library to version that includes PR UIlement: Move CoreProvider to UIElement #3669 (UIElement: Move CoreProvider to UIElement)
2. Use Adyen Dropin component in Next.js 16 app router
3. Component fails to render with context error
4. See error in browser console and call stack shows preact/hooks and CoreProvider.tsx

Expected behavior
Adyen Dropin component should render normally after library upgrade without context-related errors, maintaining the same functionality as before the upgrade.

Screenshots

Desktop:

• OS: macOS
• Browser: Safari
• Version: 26.2

Additional context

• NextJS 16.0.10 / App-router
• The issue appears to be directly related to PR UIlement: Move CoreProvider to UIElement #3669 which moved CoreProvider to UIElement base class

[johnayeni]

Hey @LouisJackson , thanks you for reporting this. Can you confirm if you are server or a client component with the Adyen Dropin?

[LouisJackson]

Hey @LouisJackson , thanks you for reporting this. Can you confirm if you are server or a client component with the Adyen Dropin?

It's a client component

[johnayeni]

Hey @LouisJackson , thanks you for reporting this. Can you confirm if you are server or a client component with the Adyen Dropin?

It's a client component

Can you share an example of your integration with the client component. I have checked using the Dropin component with a client component in Next.js 16 and could not replicate this issue. From the screenshot I might have an idea where the issue is coming from but I would like to confirm from a sample of your integration.