Problem with serialization custom property

[Pro100proff]

I have encountered with problem when I wanted to add custom property as my own object. I expected json object like this:

{
       "aps": {
        "alert": {
            "body": "body text",
            "title": "title text"
        },
        "sound": "default",
        "badge": 1
    },
    "data": {
        "deeplink": "rupodari://wallet"
    }
}

In reality, I got:

{
       "aps": {
        "alert": {
            "body": "body text",
            "title": "title text"
        },
        "sound": "default",
        "badge": 1
    },
    "data": "Data(deeplink=\"rupodari:\/\/wallet\")"
}

I checked the implementation and realised that it used toString method for the serialization custom properties.
Is there work around to solve it?

[jchambers]

Well, the docs say:

In addition to the Apple-defined keys, you may add custom keys to your payload to deliver small amounts of data to your app, notification service app extension, or notification content app extension. Your custom keys must have values with primitive types, such as dictionary, array, string, number, or Boolean. Custom keys are available in the userInfo dictionary of the UNNotificationContent object delivered to your app.

So I guess this is just a bug. I'll open an issue.

[jchambers]

I think I've misunderstood the situation and have un-marked this as the answer.

[jchambers]

Cross-posting from #974:

@Pro100proff I've looked into this a little more and I think I misunderstood your original report. To be more precisely state what I think is happening here, I understand that:

• You are using a SimpleApnsPayloadBuilder
• You are trying to set a custom property, and that value of that property is not a Java primitive, array of primitives, a Collection, or a Map

If I'm understanding you correctly, then this behavior is expected and is, in fact, documented:

pushy/pushy/src/main/java/com/eatthepath/pushy/apns/util/ApnsPayloadBuilder.java

Lines 690 to 716 in 77453f3

	/**
	* <p>Adds a custom property to the payload. According to Apple's documentation:</p>
	*
	* <blockquote>Providers can specify custom payload values outside the Apple-reserved {@code aps} namespace. Custom
	* values must use the JSON structured and primitive types: dictionary (object), array, string, number, and Boolean.
	* You should not include customer information (or any sensitive data) as custom payload data. Instead, use it for
	* such purposes as setting context (for the user interface) or internal metrics. For example, a custom payload
	* value might be a conversation identifier for use by an instant-message client application or a timestamp
	* identifying when the provider sent the notification. Any action associated with an alert message should not be
	* destructive—for example, it should not delete data on the device.</blockquote>
	*
	* <p>The value for the property is serialized to JSON as described in {@link JsonSerializer}.</p>
	*
	* @param key the key of the custom property in the payload object
	* @param value the value of the custom property
	*
	* @return a reference to this payload builder
	*
	* @throws IllegalArgumentException if the key equals to "aps"
	*/
	public ApnsPayloadBuilder addCustomProperty(final String key, final Object value) {
	if (APS_KEY.equals(key)) {
	throw new IllegalArgumentException("Custom property key must not be aps");
	}
	this.customProperties.put(key, value);
	return this;
	}

If you want to change how custom properties are serialized, you'll need to use a different ApnsPayloadBuilder implementation. Pushy offers two as separate modules: GsonApnsPayloadBuilder and JacksonApnsPayloadBuilder.

That said, I think there's room to make the documentation clearer in this case and will open a pull request to do exactly that.

[Pro100proff]

Thanks a lot for your reply!
Could you explain, why you decided to put these serializers in separate libraries?

[jchambers]

Could you explain, why you decided to put these serializers in separate libraries?

Some people want to use Gson. Some people want to use Jackson. Some people want to use neither. Moving payload builders that depend on third-party JSON libraries allows Pushy users to make a deliberate choice about which things they're adding to their classpath.