aws-sdk-android icon indicating copy to clipboard operation
aws-sdk-android copied to clipboard

Pinpoint Analytics Exceeded maximum endpoint per user count: 10

Open AlexKashi opened this issue 5 years ago • 7 comments

Same Issue as https://github.com/aws-amplify/amplify-js/issues/1378

Clearing android cache creates an additional endpoint. After multiple times the endpoint limit is reached, and none of the old endpoints are deleted.

The fix seems to be implemented in the javascript SDK but not in android.

I added - "mobiletargeting:GetUserEndpoints" to my I AM policy but that did not help.

AlexKashi avatar Sep 01 '19 19:09 AlexKashi

@AlexKashi

Is the Android cache being cleared during development and testing or this is happening at runtime in production?

mutablealligator avatar Oct 18 '19 20:10 mutablealligator

The android cache is cleared manually, similarly to aws-amplify/amplify-js#1378. Each time the cache is cleared the SDK creates a new endpoint that does not get deleted until 10 endpoints are created, and the limit is hit.

By inspecting the source code for both the android and js SDKs it seems as though the fix is only implemented in the JS SDK.

Without this edge case fixed we cannot guarantee push notifications are being delivered to our users.

AlexKashi avatar Oct 18 '19 21:10 AlexKashi

Same issue happens to our project too. What I've tried is calledaws-android-sdkpinpoint:GetUserEndpoints and open some space by deleting some of the endpoints.

But the other problem that I've encountered is on deserializing the httpResponse. Apparently com.amazonaws.services.pinpoint.model.transform.GetUserEndpointsResultJsonUnmarshaller.java is simply creating an instance return it. Thats why it's impossible to obtain the response that is successfully acquired.

orcuns avatar Nov 28 '19 13:11 orcuns

I am getting this issue on Android and aws-amplify 3.3.10

njdullea avatar Nov 24 '20 23:11 njdullea

JS fix for reference: https://github.com/aws-amplify/amplify-js/pull/2400

div5yesh avatar Sep 13 '22 19:09 div5yesh

~After investigation it looks like the Pinpoint team has implemented the following feature: when 15 endpoints are associated with a user, future endpoint updates adding new endpoints to the same user will cause the oldest endpoint to be deleted. This error should no longer be occurring.~ Edit: this is only the case for endpoints with address set; push notification-enabled endpoints are evicted in this way by Pinpoint. Please disregard.

tjleing avatar Feb 11 '23 01:02 tjleing

Making this a feature request due to the future effort required. This is still blocked by the underlying service for now.

tjleing avatar Mar 09 '23 18:03 tjleing