Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GSON warning on jdk-14 #1105

Closed
tombryden opened this issue Sep 21, 2020 · 3 comments
Closed

GSON warning on jdk-14 #1105

tombryden opened this issue Sep 21, 2020 · 3 comments
Assignees

Comments

@tombryden
Copy link

tombryden commented Sep 21, 2020

Hi,

When using methods such as Customer.retrieve() and cust.toJson() a warning is printed to console from GSON lib:

WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.google.gson.internal.reflect.UnsafeReflectionAccessor (file:/C:/Users/Tom/.m2/repository/com/google/code/gson/gson/2.8.6/gson-2.8.6.jar) to constructor java.net.Proxy()
WARNING: Please consider reporting this to the maintainers of com.google.gson.internal.reflect.UnsafeReflectionAccessor
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Seems like this issue will cause serious fault down the line if unfixed.

Thanks

@MrInterBugs
Copy link

MrInterBugs commented Mar 18, 2021

To add that it also seems to be happening somewhere in this code using JDK 15:

try {
        PaymentIntentCreateParams createParams = new PaymentIntentCreateParams.Builder()
            .setCurrency("gbp")
            .setAmount(amount)
            .setReceiptEmail(email)
            .setDescription("Blah blah")
            .build();

        PaymentIntent intent = PaymentIntent.create(createParams);
        CreatePaymentResponse paymentResponse = new CreatePaymentResponse(intent.getClientSecret());

Switch to JDK 11 and it disapears. Has any work been made on this yet?

@unsavorypeople
Copy link

It looks like this issue finally surfaced fully in JDK 16: #1190

Will there be a fix for this soon?

@dcr-stripe
Copy link
Contributor

Going to close this out as a duplicate of #1190 which has now been fixed.

Please feel free to re-open if you are still experiencing issues!

@dcr-stripe dcr-stripe closed this as not planned Won't fix, can't repro, duplicate, stale Jun 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants