[Aerogear-users] Cannot receives pushes via iOS Production variant

Matthias Wessendorf matzew at apache.org
Mon Nov 17 04:41:26 EST 2014


That should be fine

On Mon, Nov 17, 2014 at 10:32 AM, Thomas Schweitzer <thomers at me.com> wrote:

>
> On 17.11.2014, at 08:28, Matthias Wessendorf <matzew at apache.org> wrote:
>
> Should I delete my development token(s) from the DB to solve the issue
> temporarily? (I’ve got a pretty important app launch coming up, where I
> want to push to 65.000 devices…)
>
> yes, I think that's the work-around.
>
>
> thanks
>
> is it enough to
>
> DELETE FROM Installation WHERE deviceToken = “<MyDevDeviceToken>"
>
> or do i need to delete or update anything else?
>
> thx
> t
>
>
>
> We will be looking into this!
>
>
>>
>> Cheers,
>> Thomas
>>
>>
>> On 16.11.2014, at 09:30, Matthias Wessendorf <matzew at apache.org> wrote:
>>
>> Hi!
>>
>> does the production variant contain tokens from the development variant?
>>
>> -Matthias
>>
>> On Saturday, November 15, 2014, Thomas Schweitzer <thomers at me.com> wrote:
>>
>>> Hello,
>>>
>>> after upgrading to the latest AeroGear UnifiedPush Server version, I
>>> have now problems sending push notifications to iOS devices.
>>>
>>> When I select a development variant, I can send notifications via the
>>> web console, and they are received on the iOS (development) devices
>>> properly.
>>>
>>> But when I select a production variant, the notifications seem to get
>>> sent (I see no errors in the web console), and NO notifications are
>>> received on the devices. I tested this with two different apps already
>>> published in the store - same problem.
>>>
>>> >From what I can tell, there should be no difference between the app I’m
>>> testing on the dev variant, and the two apps in the store - the push
>>> registration is the same, and I can see installations for the 2 production
>>> variants, so the devices are definitely registering.
>>>
>>> The only difference is the number of receivers (4 for the dev, 50 for
>>> the production variant). I’m sending the same message.
>>>
>>> Any idea what could be wrong?
>>>
>>> Cheers,
>>> Thomas
>>>
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>
>>
>> --
>> Sent from Gmail Mobile
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>  _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20141117/2d3811f8/attachment-0001.html 


More information about the Aerogear-users mailing list