You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In pigeon version 1.6.0 it was possible to specify the apns environment (production or sandbox) when invoking APNS.push through the to: option. In the 2.0.0-rc.0 this seems to be no longer possible.
In our workflow there is a number of scenarios where we'd like to select the target APNS (production or sandbox) dynamically. A workaround is to have two pairs of the APNS adapters, so there is a voip and an app adapter per each of the two environments, four in total. While feasible, this is not ideal. Would it be possible to reinstate the to: option in the new pigeon versions?
The text was updated successfully, but these errors were encountered:
In pigeon version 1.6.0 it was possible to specify the apns environment (production or sandbox) when invoking
APNS.push
through theto:
option. In the 2.0.0-rc.0 this seems to be no longer possible.In our workflow there is a number of scenarios where we'd like to select the target APNS (production or sandbox) dynamically. A workaround is to have two pairs of the APNS adapters, so there is a voip and an app adapter per each of the two environments, four in total. While feasible, this is not ideal. Would it be possible to reinstate the
to:
option in the new pigeon versions?The text was updated successfully, but these errors were encountered: