Skip to content
This repository has been archived by the owner on Jun 11, 2021. It is now read-only.

Unexpected char 0x516b at 66 in User-Agent value #271

Closed
Francesc-Llao opened this issue Mar 14, 2016 · 4 comments
Closed

Unexpected char 0x516b at 66 in User-Agent value #271

Francesc-Llao opened this issue Mar 14, 2016 · 4 comments
Labels

Comments

@Francesc-Llao
Copy link

OUR GRADLE:
compile ('com.paypal.sdk:paypal-android-sdk:2.13.3'){
exclude group: 'io.card'
}

WHEN ERROR APPEARS:
config = new PayPalConfiguration()
.environment(PayPalConfiguration.ENVIRONMENT_PRODUCTION)
.acceptCreditCards(false)
.clientId(getString(R.string.paypal_client_id_live));

Intent intent = new Intent(this, PayPalService.class);
intent.putExtra(PayPalService.EXTRA_PAYPAL_CONFIGURATION, config);
startService(intent);

OUR CLIENT DEVICE:
Teclast P89 3G (p893g_d1h8)

OUR CLIENT ERROR:
java.lang.IllegalArgumentException: Unexpected char 0x516b at 66 in User-Agent value: PayPalSDK/PayPal-Android-SDK 2.13.3 (Android 4.4.2; Teclast P89 3G八核(D1H8); )
at okhttp3.Headers$Builder.checkNameAndValue(Headers.java:283)
at okhttp3.Headers$Builder.add(Headers.java:233)
at okhttp3.Request$Builder.addHeader(Request.java:177)
at com.paypal.android.sdk.cl.intercept(Unknown Source)
at okhttp3.RealCall$ApplicationInterceptorChain.proceed(RealCall.java:187)
at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:160)
at okhttp3.RealCall.access$100(RealCall.java:30)
at okhttp3.RealCall$AsyncCall.execute(RealCall.java:127)
at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1112)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:587)
at java.lang.Thread.run(Thread.java:841)

@jaypatel512
Copy link
Contributor

From the looks of it, it looks like the device name has a special character in it. Can you please help us confirm if you are not seeing the same issue on a different device with a non-special character please.

Thanks.

@Francesc-Llao
Copy link
Author

The error was reported by a customer.
Only happens on this device.
It is a Chinese tablet.

@jaypatel512
Copy link
Contributor

Hey @FrancescLlaoGarcia !

I think that seems like an issue in SDK side. We do accept unicode characters, but for some reason, it may be causing this issue. I will go ahead and try to reproduce and fix this issue soon.

@sankarbhavanib
Copy link
Contributor

issue resolved in 2.14.0

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants