CryptoJwt - Fix detection of firebase/php-jwt APIs #29345
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
5.70's #28971 introduced a different check for detecting firebase/php-jwt APIs. It distinguishes Firbase JWT v5.x from v6.0 -- but then it misinterprets v6.6+ and crashes.
(ping @seamuslee001 @mattwire)
Before
If you have
firebase/php-jwt
v6.6+, then it chooses the wrong behavior and gives it the v5.x-style call. This leads to errors like:After
That works.
Technical Details
The reason why the test from 28971 doesn't work is that the method signature has been moving around: