[12/05/2023 05:48:58 AM] Error fetching loading versions
[12/05/2023 05:48:58 AM] com.apollographql.apollo.exception.ApolloHttpException: HTTP 403
[12/05/2023 05:48:58 AM] at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor.parse(ApolloParseInterceptor.java:108)
[12/05/2023 05:48:58 AM] at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse(ApolloParseInterceptor.java:53)
[12/05/2023 05:48:58 AM] at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$executeHttpCall$1.onResponse(ApolloServerInterceptor.kt:114)
[12/05/2023 05:48:58 AM] at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
[12/05/2023 05:48:58 AM] at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
[12/05/2023 05:48:58 AM] at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
[12/05/2023 05:48:58 AM] at java.base/java.lang.Thread.run(Thread.java:1589)
[12/05/2023 05:48:58 AM] com.apollographql.apollo.exception.ApolloHttpException: HTTP 403
at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor.parse(ApolloParseInterceptor.java:108)
at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse(ApolloParseInterceptor.java:53)
at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$executeHttpCall$1.onResponse(ApolloServerInterceptor.kt:114)
at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:519)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642)
at java.base/java.lang.Thread.run(Thread.java:1589)
Additional Information
No response
Is this actually a launcher bug?
[X] I am sure this is a bug with the launcher and not an issue with running Minecraft
Code of Conduct
[X] I agree to follow this project's Code of Conduct
What happened?
Operating System
Windows
Relevant log output
Additional Information
No response
Is this actually a launcher bug?
Code of Conduct