TooManyProviderTokenUpdates issue on v0.15.1

Currently we use pushy v0.15.1 for our APNS push notification in a enterprise application and receive “TooManyProviderTokenUpdates” sporadically when sent a push notification to apns using .p8 file.

Below is the code to instance the ApnsClient

	private synchronized void activateApnsClient(final ConfigData activeConfigData) throws SSLException {
		if (activeConfigData != loadedConfigData) {
			closeApnsClient();
			loadedConfigData = activeConfigData;
			apnsClient = new ApnsClientBuilder()
					.setApnsServer(activeConfigData.getApnsHostName(), activeConfigData.getApnsServerport())
					.setSigningKey(activeConfigData.getApnsSigningKey())
					.setConnectionTimeout(Duration.ofSeconds(activeConfigData.getApnsConnectionTimeout(), 0))
					.setTrustedServerCertificateChain(activeConfigData.getTrustedServerCertFile())
					.build();
		}
	}

where ApnsClientBuilder.PRODUCTION_APNS_HOST and 2197 are used as Hostname and port for ApnsServer. Connection timeout is set to 5sec.

The ApnsClient will be closed and reinstantiated, when the configuration data are changed, what but seldom happens.

In our application the above code and pushy v0.14.2 are used untill 23. nov. 2021without any problem. On 24. nov. 2021 we upgraded pushy to v0.15.1using netty 4.1.69 (see #922 ). Since that time we get the response with “TooManyProviderTokenUpdates” sometimes.

Any reply is appreciated. Thanks very much.

[jchambers]

Can I donate this project?

I think you just did, friend 😉

To answer more directly, I’m not currently accepting monetary donations, but sincerely appreciate the gesture all the same.

[kicktipp]

I am glad to help. BTW: Can I donate this project?