From aamagdi at ejada.com  Mon Jan  4 08:13:16 2016
From: aamagdi at ejada.com (aamagdi)
Date: Mon, 4 Jan 2016 06:13:16 -0700 (MST)
Subject: [Aerogear-users]  UPS System Properties Custom URL
Message-ID: <1451913196211-395.post@n5.nabble.com>

Hi

I see that there exist UPS system properties to provide custom url for APNS
push servers, is there any similar property or functionality to apply the
same for Google & Microsoft servers.

Regards,
Abdalla



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-UPS-System-Properties-Custom-URL-tp395.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Mon Jan  4 08:42:02 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 4 Jan 2016 14:42:02 +0100
Subject: [Aerogear-users] UPS System Properties Custom URL
In-Reply-To: <1451913196211-395.post@n5.nabble.com>
References: <1451913196211-395.post@n5.nabble.com>
Message-ID: <CAD_dpu0Er2_HtK3zbvnr5ZdUj5F8eQXZtd7g4o+Yegj0W4CXnA@mail.gmail.com>

Hi,

For GCM, we don't have this flexibility since we rely on Google's Sender
library that provides no interface to override the endpoint URL.
 For Windows, we "own" the sender library so that could be implemented,
please open a feature request on JIRA so we can track this.

Sebi



On Mon, Jan 4, 2016 at 2:13 PM, aamagdi <aamagdi at ejada.com> wrote:

> Hi
>
> I see that there exist UPS system properties to provide custom url for APNS
> push servers, is there any similar property or functionality to apply the
> same for Google & Microsoft servers.
>
> Regards,
> Abdalla
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-UPS-System-Properties-Custom-URL-tp395.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160104/788e1f1c/attachment.html 

From aamagdi at ejada.com  Mon Jan  4 09:11:57 2016
From: aamagdi at ejada.com (aamagdi)
Date: Mon, 4 Jan 2016 07:11:57 -0700 (MST)
Subject: [Aerogear-users] UPS System Properties Custom URL
In-Reply-To: <CAD_dpu0Er2_HtK3zbvnr5ZdUj5F8eQXZtd7g4o+Yegj0W4CXnA@mail.gmail.com>
References: <1451913196211-395.post@n5.nabble.com>
	<CAD_dpu0Er2_HtK3zbvnr5ZdUj5F8eQXZtd7g4o+Yegj0W4CXnA@mail.gmail.com>
Message-ID: <1451916717656-397.post@n5.nabble.com>

OK, Thanks a lot for clarification.



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-UPS-System-Properties-Custom-URL-tp395p397.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From aamagdi at ejada.com  Mon Jan  4 09:20:04 2016
From: aamagdi at ejada.com (aamagdi)
Date: Mon, 4 Jan 2016 07:20:04 -0700 (MST)
Subject: [Aerogear-users]  Notificaiton Request Lifetime
Message-ID: <1451917204584-398.post@n5.nabble.com>

Hi,

I want to ask about the behavior of a notification request, for example if
the sever sent the request but it get a fail response or there was no
internet connection on the machine or even the server itself goes down, is
there any retry / caching mechanism and for how long?

Also what is the the maximum size of a notification request if the batch
size  is set to the default values.

Thanks a lot,
Abdalla



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Notificaiton-Request-Lifetime-tp398.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Mon Jan  4 12:02:48 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 4 Jan 2016 18:02:48 +0100
Subject: [Aerogear-users] UPS High Availability
In-Reply-To: <1451484165726-394.post@n5.nabble.com>
References: <1451484165726-394.post@n5.nabble.com>
Message-ID: <CAAg5f2STshjvhRGkKM9WmSYY0WB_cHBjDLEL4EVtEStR+jZPew@mail.gmail.com>

On Wed, Dec 30, 2015 at 3:02 PM, aamagdi <aamagdi at ejada.com> wrote:

> Hi
>
> I planning to deploy UPS 1.1 with a cluster configuration on jBoss 6.4, I
> want to ask about UPS high availability capabilities.
>
> For example for the below scenario:
> 1- A call sent to UPS rest sender api for a push notification with out
> define any aliases / variant or categories.
> 2- UPS have about 10,000 registered mobile devices.
> 3- What I have understand from UPS guide that the default batch size is
> 1000
> so this call will be split into 10 batches each batch have 1000 device, and
> UPS will start sending one batch after another.
>

yeah, for iOS it will be 2k soon:
https://github.com/aerogear/aerogear-unifiedpush-server/pull/663


> 4- After sending two batches the sever goes down or some failure occurred.
> 5- Switching to the second server node of the UPS
> Will it resume sending the request handled by the first node? or the
> request
> will lost?
>
atm we do not support this, out of the box.
Can you create a JIRA for this, so that we can schedule it ?
https://jira.jboss.org/browse/AGPUSH

Thanks,
Matthias


>
> Thanks,
> Abdalla
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/UPS-High-Availability-tp394.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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/20160104/ed69f74d/attachment.html 

From matzew at apache.org  Mon Jan  4 12:04:19 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 4 Jan 2016 18:04:19 +0100
Subject: [Aerogear-users] Notificaiton Request Lifetime
In-Reply-To: <1451917204584-398.post@n5.nabble.com>
References: <1451917204584-398.post@n5.nabble.com>
Message-ID: <CAAg5f2SA8CtM+0KiWvX5m3L8L4OuS2F62kDmp+fQ0wtksUvMDQ@mail.gmail.com>

Not yet:
https://issues.jboss.org/browse/AGPUSH-111

please comment on the ticket, and describe your needs. also, PRs are
welcome :)

On Mon, Jan 4, 2016 at 3:20 PM, aamagdi <aamagdi at ejada.com> wrote:

> Hi,
>
> I want to ask about the behavior of a notification request, for example if
> the sever sent the request but it get a fail response or there was no
> internet connection on the machine or even the server itself goes down, is
> there any retry / caching mechanism and for how long?
>
> Also what is the the maximum size of a notification request if the batch
> size  is set to the default values.
>
> Thanks a lot,
> Abdalla
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Notificaiton-Request-Lifetime-tp398.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> 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/20160104/fe4fcf6d/attachment.html 

From nmartin at appstud.me  Wed Jan  6 05:54:43 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Wed, 6 Jan 2016 10:54:43 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
Message-ID: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>

Hi !

I would like to know if you updated the cocoapod for your latest release of aerogear-ios-sync-client ?

There?s no way I can compile, I still have error like these:

[cid:738FBFAA-596C-49B5-A2E3-F0C4D54409DA]

So this is related with another pod but still I think the project aerogear-ios-sync-client is not correctly updated

Best regards,

Nataniel.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160106/84995bc7/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-01-06 at 14.54.41.png
Type: image/png
Size: 804790 bytes
Desc: Screen Shot 2016-01-06 at 14.54.41.png
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20160106/84995bc7/attachment-0001.png 

From corinnekrych at gmail.com  Thu Jan  7 08:34:07 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Thu, 7 Jan 2016 14:34:07 +0100
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
Message-ID: <CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not
using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax)
whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version
on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1]
https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160107/b04838a3/attachment.html 

From eug.bab at gmail.com  Thu Jan  7 22:56:45 2016
From: eug.bab at gmail.com (eugeneb)
Date: Thu, 7 Jan 2016 20:56:45 -0700 (MST)
Subject: [Aerogear-users] Android sound and vibrate
Message-ID: <1452225405997-403.post@n5.nabble.com>

Is any way to disable notification sound and vibrate for Android from this
plugin?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From edewit at redhat.com  Fri Jan  8 02:33:24 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 8 Jan 2016 08:33:24 +0100
Subject: [Aerogear-users] Android sound and vibrate
In-Reply-To: <1452225405997-403.post@n5.nabble.com>
References: <1452225405997-403.post@n5.nabble.com>
Message-ID: <CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>

The plugin doesn't set sound and vibration, maybe that is something that is
set on os level.

On Fri, Jan 8, 2016 at 4:56 AM, eugeneb <eug.bab at gmail.com> wrote:

> Is any way to disable notification sound and vibrate for Android from this
> plugin?
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/a5d79872/attachment.html 

From nmartin at appstud.me  Fri Jan  8 02:39:42 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Fri, 8 Jan 2016 07:39:42 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
Message-ID: <D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>

Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/3829b500/attachment.html 

From corinnekrych at gmail.com  Fri Jan  8 03:01:12 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 8 Jan 2016 09:01:12 +0100
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
Message-ID: <CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which
update to Swift 2 syntax) did not make it to cocoapods although we did have
a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work
around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2]
https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me> wrote:

> Hi,
> Thanks for your response.
>
> It?s still not working with this configuration:
>
> *PODFILE:*
>
> source 'https://github.com/CocoaPods/Specs.git'
>
> platform :ios, '8.0'
> platform :ios, :deployment_target => '8.0'
> xcodeproj 'TestAerogear.xcodeproj'
> use_frameworks!
>
> pod '*AeroGearSyncClient*'
> pod '*Starscream*', '~> 1.0?
>
> ?
>
> *POD INSTALL:*
>
> CocoaPods 1.0.0.beta.2 is available.
> To update use: `gem install cocoapods --pre`
> [!] This is a test version we'd love you to try.
>
> For more information see http://blog.cocoapods.org
> and the CHANGELOG for this version http://git.io/BaH8pQ.
>
> Analyzing dependencies
> [!] Unable to satisfy the following requirements:
>
> - `Starscream (~> 1.0)` required by `Podfile`
> - `Starscream (= 0.9.3)` required by `Podfile.lock`
>
> Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but
> they required a higher minimum deployment target.
>
> On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> Hello Nataniel,
>
> By the look of the errors it seems the Swift syntax of starscream is not
> using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax)
> whereas joinWithSeparator() is Swift 2 syntax).
> In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version
> on master. Previous version of the lib used Swift 1 syntax.
>
> ++
> Corinne
> [1]
> https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8
>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/3b464283/attachment-0001.html 

From nmartin at appstud.me  Fri Jan  8 03:08:38 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Fri, 8 Jan 2016 08:08:38 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
Message-ID: <BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>

Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/093079a3/attachment.html 

From corinnekrych at gmail.com  Fri Jan  8 03:10:08 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 8 Jan 2016 09:10:08 +0100
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
Message-ID: <CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me> wrote:

> Hi,
>
> Thanks for the swift reply :)
>
> Looking forward for the new version !
>
> But using the exemple in [2] such as:
>
> *source 'https://github.com/CocoaPods/Specs.git'
> <https://github.com/CocoaPods/Specs.git'>*
>
> *platform :ios, '8.0'*
> *platform :ios, :deployment_target => '8.0'*
> *xcodeproj 'TestAerogear.xcodeproj'*
> *use_frameworks!*
>
> *pod 'AeroGearSyncClient', :git =>
> 'https://github.com/aerogear/aerogear-ios-sync-client'
> <https://github.com/aerogear/aerogear-ios-sync-client'>*
>
> Still give me some errors like these:
>
> Analyzing dependencies
> Pre-downloading: `AeroGearSyncClient` from `
> https://github.com/aerogear/aerogear-ios-sync-client`
> <https://github.com/aerogear/aerogear-ios-sync-client>
> [!] Unable to find a specification for 'AeroGearSyncClient'.
>
> I think the problem is related when you lint the pod.
>
> Best regards !
>
> On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> Hi
>
> Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3
> (which update to Swift 2 syntax) did not make it to cocoapods although we
> did have a tag for it [1].
> 1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
> I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work
> around), please us the latest git master version as shown [2].
>
> ++
> Corinne
> [1]
> https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
> [2]
> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7
>
> On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me> wrote:
>
>> Hi,
>> Thanks for your response.
>>
>> It?s still not working with this configuration:
>>
>> *PODFILE:*
>>
>> source 'https://github.com/CocoaPods/Specs.git'
>>
>> platform :ios, '8.0'
>> platform :ios, :deployment_target => '8.0'
>> xcodeproj 'TestAerogear.xcodeproj'
>> use_frameworks!
>>
>> pod '*AeroGearSyncClient*'
>> pod '*Starscream*', '~> 1.0?
>>
>> ?
>>
>> *POD INSTALL:*
>>
>> CocoaPods 1.0.0.beta.2 is available.
>> To update use: `gem install cocoapods --pre`
>> [!] This is a test version we'd love you to try.
>>
>> For more information see http://blog.cocoapods.org
>> and the CHANGELOG for this version http://git.io/BaH8pQ.
>>
>> Analyzing dependencies
>> [!] Unable to satisfy the following requirements:
>>
>> - `Starscream (~> 1.0)` required by `Podfile`
>> - `Starscream (= 0.9.3)` required by `Podfile.lock`
>>
>> Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but
>> they required a higher minimum deployment target.
>>
>> On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com> wrote:
>>
>> Hello Nataniel,
>>
>> By the look of the errors it seems the Swift syntax of starscream is not
>> using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax)
>> whereas joinWithSeparator() is Swift 2 syntax).
>> In Podfile[1] check you're pointing to starscream 1.0.2+ or latest
>> version on master. Previous version of the lib used Swift 1 syntax.
>>
>> ++
>> Corinne
>> [1]
>> https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8
>>
>> _______________________________________________
>> 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
>>
>>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/22d24695/attachment-0001.html 

From nmartin at appstud.me  Fri Jan  8 03:15:19 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Fri, 8 Jan 2016 08:15:19 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
Message-ID: <23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>

The cocoa pod version is:
0.39.0

It?s the latest, not the last beta version that is 1.0.0.beta.2

Regards,
Nataniel

On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`<https://github.com/aerogear/aerogear-ios-sync-client>
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/0a849e8e/attachment.html 

From corinnekrych at gmail.com  Fri Jan  8 03:44:03 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Fri, 8 Jan 2016 09:44:03 +0100
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
Message-ID: <CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>

Hi Nataniel

Sorry my bad the pod on master are expressed slightly different (no subpod
anymore) see correct syntax [1]. Replace AeroGearSyncClient by
 AeroGearSyncClientJsonPatch.
This is a workaround until i do proper release.
++
Corinne
[1]
https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me> wrote:

> The cocoa pod version is:
> *0.39.0*
>
> It?s the latest, not the last beta version that is 1.0.0.beta.2
>
> Regards,
> Nataniel
>
> On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> Which cocoapods version are you on?
> ++
> Corinne
>
> On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me> wrote:
>
>> Hi,
>>
>> Thanks for the swift reply :)
>>
>> Looking forward for the new version !
>>
>> But using the exemple in [2] such as:
>>
>> *source 'https://github.com/CocoaPods/Specs.git'
>> <https://github.com/CocoaPods/Specs.git'>*
>>
>> *platform :ios, '8.0'*
>> *platform :ios, :deployment_target => '8.0'*
>> *xcodeproj 'TestAerogear.xcodeproj'*
>> *use_frameworks!*
>>
>> *pod 'AeroGearSyncClient', :git =>
>> 'https://github.com/aerogear/aerogear-ios-sync-client'
>> <https://github.com/aerogear/aerogear-ios-sync-client'>*
>>
>> Still give me some errors like these:
>>
>> Analyzing dependencies
>> Pre-downloading: `AeroGearSyncClient` from `
>> https://github.com/aerogear/aerogear-ios-sync-client`
>> <https://github.com/aerogear/aerogear-ios-sync-client>
>> [!] Unable to find a specification for 'AeroGearSyncClient'.
>>
>> I think the problem is related when you lint the pod.
>>
>> Best regards !
>>
>> On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com> wrote:
>>
>> Hi
>>
>> Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3
>> (which update to Swift 2 syntax) did not make it to cocoapods although we
>> did have a tag for it [1].
>> 1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
>> I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work
>> around), please us the latest git master version as shown [2].
>>
>> ++
>> Corinne
>> [1]
>> https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
>> [2]
>> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7
>>
>> On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me> wrote:
>>
>>> Hi,
>>> Thanks for your response.
>>>
>>> It?s still not working with this configuration:
>>>
>>> *PODFILE:*
>>>
>>> source 'https://github.com/CocoaPods/Specs.git'
>>>
>>> platform :ios, '8.0'
>>> platform :ios, :deployment_target => '8.0'
>>> xcodeproj 'TestAerogear.xcodeproj'
>>> use_frameworks!
>>>
>>> pod '*AeroGearSyncClient*'
>>> pod '*Starscream*', '~> 1.0?
>>>
>>> ?
>>>
>>> *POD INSTALL:*
>>>
>>> CocoaPods 1.0.0.beta.2 is available.
>>> To update use: `gem install cocoapods --pre`
>>> [!] This is a test version we'd love you to try.
>>>
>>> For more information see http://blog.cocoapods.org
>>> and the CHANGELOG for this version http://git.io/BaH8pQ.
>>>
>>> Analyzing dependencies
>>> [!] Unable to satisfy the following requirements:
>>>
>>> - `Starscream (~> 1.0)` required by `Podfile`
>>> - `Starscream (= 0.9.3)` required by `Podfile.lock`
>>>
>>> Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but
>>> they required a higher minimum deployment target.
>>>
>>> On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>
>>> Hello Nataniel,
>>>
>>> By the look of the errors it seems the Swift syntax of starscream is not
>>> using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax)
>>> whereas joinWithSeparator() is Swift 2 syntax).
>>> In Podfile[1] check you're pointing to starscream 1.0.2+ or latest
>>> version on master. Previous version of the lib used Swift 1 syntax.
>>>
>>> ++
>>> Corinne
>>> [1]
>>> https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8
>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>> _______________________________________________
>> 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
>>
>>
> _______________________________________________
> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/0f3c4181/attachment-0001.html 

From nmartin at appstud.me  Fri Jan  8 06:02:49 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Fri, 8 Jan 2016 11:02:49 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
Message-ID: <007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>

Hi,

It?s seems to be better that way !

It would like to point you out that with this workaround, even with the Jedi Demo project, there are two errors while building the project:

[cid:D3F7DB2E-EA6E-4D80-A2C4-C4F2DCE5B350]

It seems that the import of JSONTools file is not correctly bridged for AeroGearSyncJsonPatch.

Best regards,

Nataniel

On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi Nataniel

Sorry my bad the pod on master are expressed slightly different (no subpod anymore) see correct syntax [1]. Replace AeroGearSyncClient by  AeroGearSyncClientJsonPatch.
This is a workaround until i do proper release.
++
Corinne
[1] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
The cocoa pod version is:
0.39.0

It?s the latest, not the last beta version that is 1.0.0.beta.2

Regards,
Nataniel

On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`<https://github.com/aerogear/aerogear-ios-sync-client>
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/8f3f2625/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2016-01-08 at 14.52.05.png
Type: image/png
Size: 75865 bytes
Desc: Screen Shot 2016-01-08 at 14.52.05.png
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20160108/8f3f2625/attachment-0001.png 

From eug.bab at gmail.com  Fri Jan  8 09:30:36 2016
From: eug.bab at gmail.com (eugeneb)
Date: Fri, 8 Jan 2016 07:30:36 -0700 (MST)
Subject: [Aerogear-users] Android sound and vibrate
In-Reply-To: <CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>
References: <1452225405997-403.post@n5.nabble.com>
	<CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>
Message-ID: <1452263436154-412.post@n5.nabble.com>

Thank you Erik for your quick answer.
Based on
http://stackoverflow.com/questions/7655164/android-notification-sound-disable
I see it can be done on plugin level.
For Ios devices I can control sound from the backend. In Android so far I
see I can only provide custom sound file in payload 
https://developers.google.com/cloud-messaging/http-server-ref, and still it
doesn't have vibrate control. So even if I provide quite sound file I can't
disable vibrate. 
Latest Android OS doesn't provide notification sound/vibrate control on app
level.
Still looking for right solution. Any other ideas?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403p412.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From nmartin at appstud.me  Mon Jan 11 02:54:40 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Mon, 11 Jan 2016 07:54:40 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
	<007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
Message-ID: <C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>

Hi !

Any news on these errors ?

I tried a few things on it, but I can?t make it compile :(

Looking forward reading to reading from you.

Nataniel.

On 08 Jan 2016, at 15:02, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi,

It?s seems to be better that way !

It would like to point you out that with this workaround, even with the Jedi Demo project, there are two errors while building the project:

<Screen Shot 2016-01-08 at 14.52.05.png>

It seems that the import of JSONTools file is not correctly bridged for AeroGearSyncJsonPatch.

Best regards,

Nataniel

On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi Nataniel

Sorry my bad the pod on master are expressed slightly different (no subpod anymore) see correct syntax [1]. Replace AeroGearSyncClient by  AeroGearSyncClientJsonPatch.
This is a workaround until i do proper release.
++
Corinne
[1] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
The cocoa pod version is:
0.39.0

It?s the latest, not the last beta version that is 1.0.0.beta.2

Regards,
Nataniel

On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`<https://github.com/aerogear/aerogear-ios-sync-client>
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/d733c854/attachment-0001.html 

From edewit at redhat.com  Mon Jan 11 03:12:32 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 11 Jan 2016 09:12:32 +0100
Subject: [Aerogear-users] Android sound and vibrate
In-Reply-To: <1452263436154-412.post@n5.nabble.com>
References: <1452225405997-403.post@n5.nabble.com>
	<CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>
	<1452263436154-412.post@n5.nabble.com>
Message-ID: <CAO2B-fbdweA54GWYdd0jS-pc=ssVyTF=zh7jX5ENRY3jEknfcg@mail.gmail.com>

So all includes vibration, well in that case you could try and see if
changing this line[1] to 'Notification.DEFAULT_LIGHTS'

[1]
https://github.com/aerogear/aerogear-cordova-push/blob/acb7b6b33d636ed5462a7d7ca7d3c09ec81e5575/src/android/org/jboss/aerogear/cordova/push/NotificationMessageHandler.java#L87

On Fri, Jan 8, 2016 at 3:30 PM, eugeneb <eug.bab at gmail.com> wrote:

> Thank you Erik for your quick answer.
> Based on
>
> http://stackoverflow.com/questions/7655164/android-notification-sound-disable
> I see it can be done on plugin level.
> For Ios devices I can control sound from the backend. In Android so far I
> see I can only provide custom sound file in payload
> https://developers.google.com/cloud-messaging/http-server-ref, and still
> it
> doesn't have vibrate control. So even if I provide quite sound file I can't
> disable vibrate.
> Latest Android OS doesn't provide notification sound/vibrate control on app
> level.
> Still looking for right solution. Any other ideas?
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403p412.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/403444b5/attachment.html 

From nmartin at appstud.me  Mon Jan 11 03:42:01 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Mon, 11 Jan 2016 08:42:01 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
	<007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
	<C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>
Message-ID: <8919F509-2BAA-468D-B5B7-DEC345B20221@appstud.me>

By the way Corrinne,

What version of Xcode / SWIFT are you using ?

FYI I?m using Xcode 7.2 + Swift 2.1.

Seems that flags are not correctly set.

Best regards,

Nataniel

On 11 Jan 2016, at 11:54, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi !

Any news on these errors ?

I tried a few things on it, but I can?t make it compile :(

Looking forward reading to reading from you.

Nataniel.

On 08 Jan 2016, at 15:02, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi,

It?s seems to be better that way !

It would like to point you out that with this workaround, even with the Jedi Demo project, there are two errors while building the project:

<Screen Shot 2016-01-08 at 14.52.05.png>

It seems that the import of JSONTools file is not correctly bridged for AeroGearSyncJsonPatch.

Best regards,

Nataniel

On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi Nataniel

Sorry my bad the pod on master are expressed slightly different (no subpod anymore) see correct syntax [1]. Replace AeroGearSyncClient by  AeroGearSyncClientJsonPatch.
This is a workaround until i do proper release.
++
Corinne
[1] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
The cocoa pod version is:
0.39.0

It?s the latest, not the last beta version that is 1.0.0.beta.2

Regards,
Nataniel

On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`<https://github.com/aerogear/aerogear-ios-sync-client>
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/27c4c791/attachment-0001.html 

From corinnekrych at gmail.com  Mon Jan 11 05:28:04 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 11 Jan 2016 11:28:04 +0100
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <8919F509-2BAA-468D-B5B7-DEC345B20221@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
	<007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
	<C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>
	<8919F509-2BAA-468D-B5B7-DEC345B20221@appstud.me>
Message-ID: <CAL8vO=d0=PCUeeWYYmD5qmJM0tb5c0sdDt1NumsZDKCtZ51VSQ@mail.gmail.com>

Hello Nataniel,

I use Xcode 7.2, cocoapods 0.39.0 like you and I faced the same issue.

To sort out the issue, I've defined a new podspec for the ObjC dependencies
JSONTools and KiteValidator. Mainly, I rework the import statement and
define a modulemap for both libraries.

As we don't directly own the libs I'll issue a PR and start the discussion.
Once it's merged we can do a new cocoapods release. In the mean time, you
can try it with these fork/branch, in your Podfile, try [1]. Let me know
how it goes for you.

++
Corinne.
[1]
https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/8cea70682c2e57028100405fca1171343b07b5be/Jedi/JsonPatchSync/Podfile#L7-L10

On 11 January 2016 at 09:42, Nataniel Martin <nmartin at appstud.me> wrote:

> By the way Corrinne,
>
> What version of Xcode / SWIFT are you using ?
>
> FYI I?m using Xcode 7.2 + Swift 2.1.
>
> Seems that flags are not correctly set.
>
> Best regards,
>
> Nataniel
>
> On 11 Jan 2016, at 11:54, Nataniel Martin <nmartin at appstud.me> wrote:
>
> Hi !
>
> Any news on these errors ?
>
> I tried a few things on it, but I can?t make it compile :(
>
> Looking forward reading to reading from you.
>
> Nataniel.
>
> On 08 Jan 2016, at 15:02, Nataniel Martin <nmartin at appstud.me> wrote:
>
> Hi,
>
> It?s seems to be better that way !
>
> It would like to point you out that with this workaround, even with the
> Jedi Demo project, there are two errors while building the project:
>
> <Screen Shot 2016-01-08 at 14.52.05.png>
>
> It seems that the import of JSONTools file is not correctly bridged for
> AeroGearSyncJsonPatch.
>
> Best regards,
>
> Nataniel
>
> On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> Hi Nataniel
>
> Sorry my bad the pod on master are expressed slightly different (no subpod
> anymore) see correct syntax [1]. Replace AeroGearSyncClient by
>  AeroGearSyncClientJsonPatch.
> This is a workaround until i do proper release.
> ++
> Corinne
> [1]
> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7
>
> On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me> wrote:
>
>> The cocoa pod version is:
>> *0.39.0*
>>
>> It?s the latest, not the last beta version that is 1.0.0.beta.2
>>
>> Regards,
>> Nataniel
>>
>> On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com> wrote:
>>
>> Which cocoapods version are you on?
>> ++
>> Corinne
>>
>> On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me> wrote:
>>
>>> Hi,
>>>
>>> Thanks for the swift reply :)
>>>
>>> Looking forward for the new version !
>>>
>>> But using the exemple in [2] such as:
>>>
>>> *source 'https://github.com/CocoaPods/Specs.git'
>>> <https://github.com/CocoaPods/Specs.git'>*
>>>
>>> *platform :ios, '8.0'*
>>> *platform :ios, :deployment_target => '8.0'*
>>> *xcodeproj 'TestAerogear.xcodeproj'*
>>> *use_frameworks!*
>>>
>>> *pod 'AeroGearSyncClient', :git =>
>>> 'https://github.com/aerogear/aerogear-ios-sync-client'
>>> <https://github.com/aerogear/aerogear-ios-sync-client'>*
>>>
>>> Still give me some errors like these:
>>>
>>> Analyzing dependencies
>>> Pre-downloading: `AeroGearSyncClient` from `
>>> https://github.com/aerogear/aerogear-ios-sync-client`
>>> <https://github.com/aerogear/aerogear-ios-sync-client>
>>> [!] Unable to find a specification for 'AeroGearSyncClient'.
>>>
>>> I think the problem is related when you lint the pod.
>>>
>>> Best regards !
>>>
>>> On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>
>>> Hi
>>>
>>> Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3
>>> (which update to Swift 2 syntax) did not make it to cocoapods although we
>>> did have a tag for it [1].
>>> 1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
>>> I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work
>>> around), please us the latest git master version as shown [2].
>>>
>>> ++
>>> Corinne
>>> [1]
>>> https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
>>> [2]
>>> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7
>>>
>>> On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me> wrote:
>>>
>>>> Hi,
>>>> Thanks for your response.
>>>>
>>>> It?s still not working with this configuration:
>>>>
>>>> *PODFILE:*
>>>>
>>>> source 'https://github.com/CocoaPods/Specs.git'
>>>>
>>>> platform :ios, '8.0'
>>>> platform :ios, :deployment_target => '8.0'
>>>> xcodeproj 'TestAerogear.xcodeproj'
>>>> use_frameworks!
>>>>
>>>> pod '*AeroGearSyncClient*'
>>>> pod '*Starscream*', '~> 1.0?
>>>>
>>>> ?
>>>>
>>>> *POD INSTALL:*
>>>>
>>>> CocoaPods 1.0.0.beta.2 is available.
>>>> To update use: `gem install cocoapods --pre`
>>>> [!] This is a test version we'd love you to try.
>>>>
>>>> For more information see http://blog.cocoapods.org
>>>> and the CHANGELOG for this version http://git.io/BaH8pQ.
>>>>
>>>> Analyzing dependencies
>>>> [!] Unable to satisfy the following requirements:
>>>>
>>>> - `Starscream (~> 1.0)` required by `Podfile`
>>>> - `Starscream (= 0.9.3)` required by `Podfile.lock`
>>>>
>>>> Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but
>>>> they required a higher minimum deployment target.
>>>>
>>>> On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>>
>>>> Hello Nataniel,
>>>>
>>>> By the look of the errors it seems the Swift syntax of starscream is
>>>> not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax)
>>>> whereas joinWithSeparator() is Swift 2 syntax).
>>>> In Podfile[1] check you're pointing to starscream 1.0.2+ or latest
>>>> version on master. Previous version of the lib used Swift 1 syntax.
>>>>
>>>> ++
>>>> Corinne
>>>> [1]
>>>> https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8
>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>> _______________________________________________
>> 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
>>
>>
> _______________________________________________
> 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
>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/ead9d491/attachment.html 

From nmartin at appstud.me  Mon Jan 11 06:51:13 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Mon, 11 Jan 2016 11:51:13 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=d0=PCUeeWYYmD5qmJM0tb5c0sdDt1NumsZDKCtZ51VSQ@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
	<007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
	<C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>
	<8919F509-2BAA-468D-B5B7-DEC345B20221@appstud.me>
	<CAL8vO=d0=PCUeeWYYmD5qmJM0tb5c0sdDt1NumsZDKCtZ51VSQ@mail.gmail.com>
Message-ID: <097DABD6-45E4-46E3-809E-CEB983218A44@appstud.me>

Hi Corrinne,

Thanks you very much for your help !

So this is what it came out with my testings:

1) First the Podfile used a private library: for KiteValidator;
So in order to work that out, had to slightly modify the Podfile like this :
pod 'KiteJSONValidator', :git => 'https://github.com/corinnekrych/KiteJSONValidator.git', :branch => 'podspec.public.header'


2) The import in ViewController.swift from the project : aerogear-ios-cookbook/Jedi/JsonPatchSync

import AeroGearSync
import AeroGearSyncClient

Had to be changed like this:

import AeroGearSyncJsonPatch
import AeroGearSyncClientJsonPatch

3) Now i?m facing a other problem :

private var syncClient: SyncClient<JsonPatchSynchronizer, InMemoryDataStore<JsonNode, JsonPatchEdit>>

SyncClient type is unrecognised by the Xcode (even after a build clean)

-----

This were i?m blocked. But i feel that we are not that far from the solution :)

Let me know if I did something wrong along my explanation.

Best regards !

Nataniel

On 11 Jan 2016, at 14:28, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

I use Xcode 7.2, cocoapods 0.39.0 like you and I faced the same issue.

To sort out the issue, I've defined a new podspec for the ObjC dependencies JSONTools and KiteValidator. Mainly, I rework the import statement and define a modulemap for both libraries.

As we don't directly own the libs I'll issue a PR and start the discussion. Once it's merged we can do a new cocoapods release. In the mean time, you can try it with these fork/branch, in your Podfile, try [1]. Let me know how it goes for you.

++
Corinne.
[1] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/8cea70682c2e57028100405fca1171343b07b5be/Jedi/JsonPatchSync/Podfile#L7-L10

On 11 January 2016 at 09:42, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
By the way Corrinne,

What version of Xcode / SWIFT are you using ?

FYI I?m using Xcode 7.2 + Swift 2.1.

Seems that flags are not correctly set.

Best regards,

Nataniel

On 11 Jan 2016, at 11:54, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi !

Any news on these errors ?

I tried a few things on it, but I can?t make it compile :(

Looking forward reading to reading from you.

Nataniel.

On 08 Jan 2016, at 15:02, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi,

It?s seems to be better that way !

It would like to point you out that with this workaround, even with the Jedi Demo project, there are two errors while building the project:

<Screen Shot 2016-01-08 at 14.52.05.png>

It seems that the import of JSONTools file is not correctly bridged for AeroGearSyncJsonPatch.

Best regards,

Nataniel

On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi Nataniel

Sorry my bad the pod on master are expressed slightly different (no subpod anymore) see correct syntax [1]. Replace AeroGearSyncClient by  AeroGearSyncClientJsonPatch.
This is a workaround until i do proper release.
++
Corinne
[1] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
The cocoa pod version is:
0.39.0

It?s the latest, not the last beta version that is 1.0.0.beta.2

Regards,
Nataniel

On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`<https://github.com/aerogear/aerogear-ios-sync-client>
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/6d35aa03/attachment-0001.html 

From corinnekrych at gmail.com  Mon Jan 11 07:40:00 2016
From: corinnekrych at gmail.com (Corinne Krych)
Date: Mon, 11 Jan 2016 13:40:00 +0100
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <097DABD6-45E4-46E3-809E-CEB983218A44@appstud.me>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
	<007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
	<C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>
	<8919F509-2BAA-468D-B5B7-DEC345B20221@appstud.me>
	<CAL8vO=d0=PCUeeWYYmD5qmJM0tb5c0sdDt1NumsZDKCtZ51VSQ@mail.gmail.com>
	<097DABD6-45E4-46E3-809E-CEB983218A44@appstud.me>
Message-ID: <CAL8vO=fgjBbm1d3E4iDxGSmRFyEp3jVxa3iCwEVMfu6G_uhxFw@mail.gmail.com>

Hi Nataniel

I did the same steps you described to solve the last issue, go to
AeroGeatSyncDemo target, select build settings and set:
ONLY_ACTIVE_ARCH = YES;
Then delete do a clean build (delete DerivedData)

Let me know how it goes for you. I'll issue a PR on Jedi cookbook.

++
Corinne

On 11 January 2016 at 12:51, Nataniel Martin <nmartin at appstud.me> wrote:

> Hi Corrinne,
>
> Thanks you very much for your help !
>
> So this is what it came out with my testings:
>
> 1) First the Podfile used a private library: for KiteValidator;
> So in order to work that out, had to slightly modify the Podfile like this
> :
> pod 'KiteJSONValidator', :git => 'https://github.com*/*corinnekrych/KiteJSONValidator.git',
> :branch => 'podspec.public.header'
>
>
> 2) The import in* ViewController.swift *from the project :
> aerogear-ios-cookbook/Jedi/JsonPatchSync
>
> import AeroGearSync
> import AeroGearSyncClient
>
> Had to be changed like this:
>
> import AeroGearSyncJsonPatch
> import AeroGearSyncClientJsonPatch
>
> 3) Now i?m facing a other problem :
>
> private var syncClient: SyncClient<JsonPatchSynchronizer,
> InMemoryDataStore<JsonNode, JsonPatchEdit>>
>
> *SyncClient* type is unrecognised by the Xcode (even after a build clean)
>
> -----
>
> This were i?m blocked. But i feel that we are not that far from the
> solution :)
>
> Let me know if I did something wrong along my explanation.
>
> Best regards !
>
> Nataniel
>
> On 11 Jan 2016, at 14:28, Corinne Krych <corinnekrych at gmail.com> wrote:
>
> Hello Nataniel,
>
> I use Xcode 7.2, cocoapods 0.39.0 like you and I faced the same issue.
>
> To sort out the issue, I've defined a new podspec for the ObjC
> dependencies JSONTools and KiteValidator. Mainly, I rework the import
> statement and define a modulemap for both libraries.
>
> As we don't directly own the libs I'll issue a PR and start the
> discussion. Once it's merged we can do a new cocoapods release. In the mean
> time, you can try it with these fork/branch, in your Podfile, try [1]. Let
> me know how it goes for you.
>
> ++
> Corinne.
> [1]
> https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/8cea70682c2e57028100405fca1171343b07b5be/Jedi/JsonPatchSync/Podfile#L7-L10
>
> On 11 January 2016 at 09:42, Nataniel Martin <nmartin at appstud.me> wrote:
>
>> By the way Corrinne,
>>
>> What version of Xcode / SWIFT are you using ?
>>
>> FYI I?m using Xcode 7.2 + Swift 2.1.
>>
>> Seems that flags are not correctly set.
>>
>> Best regards,
>>
>> Nataniel
>>
>> On 11 Jan 2016, at 11:54, Nataniel Martin <nmartin at appstud.me> wrote:
>>
>> Hi !
>>
>> Any news on these errors ?
>>
>> I tried a few things on it, but I can?t make it compile :(
>>
>> Looking forward reading to reading from you.
>>
>> Nataniel.
>>
>> On 08 Jan 2016, at 15:02, Nataniel Martin <nmartin at appstud.me> wrote:
>>
>> Hi,
>>
>> It?s seems to be better that way !
>>
>> It would like to point you out that with this workaround, even with the
>> Jedi Demo project, there are two errors while building the project:
>>
>> <Screen Shot 2016-01-08 at 14.52.05.png>
>>
>> It seems that the import of JSONTools file is not correctly bridged for
>> AeroGearSyncJsonPatch.
>>
>> Best regards,
>>
>> Nataniel
>>
>> On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com> wrote:
>>
>> Hi Nataniel
>>
>> Sorry my bad the pod on master are expressed slightly different (no
>> subpod anymore) see correct syntax [1]. Replace AeroGearSyncClient by
>>  AeroGearSyncClientJsonPatch.
>> This is a workaround until i do proper release.
>> ++
>> Corinne
>> [1]
>> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7
>>
>> On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me> wrote:
>>
>>> The cocoa pod version is:
>>> *0.39.0*
>>>
>>> It?s the latest, not the last beta version that is 1.0.0.beta.2
>>>
>>> Regards,
>>> Nataniel
>>>
>>> On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>
>>> Which cocoapods version are you on?
>>> ++
>>> Corinne
>>>
>>> On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me> wrote:
>>>
>>>> Hi,
>>>>
>>>> Thanks for the swift reply :)
>>>>
>>>> Looking forward for the new version !
>>>>
>>>> But using the exemple in [2] such as:
>>>>
>>>> *source 'https://github.com/CocoaPods/Specs.git'
>>>> <https://github.com/CocoaPods/Specs.git'>*
>>>>
>>>> *platform :ios, '8.0'*
>>>> *platform :ios, :deployment_target => '8.0'*
>>>> *xcodeproj 'TestAerogear.xcodeproj'*
>>>> *use_frameworks!*
>>>>
>>>> *pod 'AeroGearSyncClient', :git =>
>>>> 'https://github.com/aerogear/aerogear-ios-sync-client'
>>>> <https://github.com/aerogear/aerogear-ios-sync-client'>*
>>>>
>>>> Still give me some errors like these:
>>>>
>>>> Analyzing dependencies
>>>> Pre-downloading: `AeroGearSyncClient` from `
>>>> https://github.com/aerogear/aerogear-ios-sync-client`
>>>> <https://github.com/aerogear/aerogear-ios-sync-client>
>>>> [!] Unable to find a specification for 'AeroGearSyncClient'.
>>>>
>>>> I think the problem is related when you lint the pod.
>>>>
>>>> Best regards !
>>>>
>>>> On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com> wrote:
>>>>
>>>> Hi
>>>>
>>>> Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3
>>>> (which update to Swift 2 syntax) did not make it to cocoapods although we
>>>> did have a tag for it [1].
>>>> 1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
>>>> I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work
>>>> around), please us the latest git master version as shown [2].
>>>>
>>>> ++
>>>> Corinne
>>>> [1]
>>>> https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
>>>> [2]
>>>> https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7
>>>>
>>>> On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me> wrote:
>>>>
>>>>> Hi,
>>>>> Thanks for your response.
>>>>>
>>>>> It?s still not working with this configuration:
>>>>>
>>>>> *PODFILE:*
>>>>>
>>>>> source 'https://github.com/CocoaPods/Specs.git'
>>>>>
>>>>> platform :ios, '8.0'
>>>>> platform :ios, :deployment_target => '8.0'
>>>>> xcodeproj 'TestAerogear.xcodeproj'
>>>>> use_frameworks!
>>>>>
>>>>> pod '*AeroGearSyncClient*'
>>>>> pod '*Starscream*', '~> 1.0?
>>>>>
>>>>> ?
>>>>>
>>>>> *POD INSTALL:*
>>>>>
>>>>> CocoaPods 1.0.0.beta.2 is available.
>>>>> To update use: `gem install cocoapods --pre`
>>>>> [!] This is a test version we'd love you to try.
>>>>>
>>>>> For more information see http://blog.cocoapods.org
>>>>> and the CHANGELOG for this version http://git.io/BaH8pQ.
>>>>>
>>>>> Analyzing dependencies
>>>>> [!] Unable to satisfy the following requirements:
>>>>>
>>>>> - `Starscream (~> 1.0)` required by `Podfile`
>>>>> - `Starscream (= 0.9.3)` required by `Podfile.lock`
>>>>>
>>>>> Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but
>>>>> they required a higher minimum deployment target.
>>>>>
>>>>> On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hello Nataniel,
>>>>>
>>>>> By the look of the errors it seems the Swift syntax of starscream is
>>>>> not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax)
>>>>> whereas joinWithSeparator() is Swift 2 syntax).
>>>>> In Podfile[1] check you're pointing to starscream 1.0.2+ or latest
>>>>> version on master. Previous version of the lib used Swift 1 syntax.
>>>>>
>>>>> ++
>>>>> Corinne
>>>>> [1]
>>>>> https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>>
>>>>>
>>>> _______________________________________________
>>>> 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
>>>>
>>>>
>>> _______________________________________________
>>> 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
>>>
>>>
>> _______________________________________________
>> 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
>>
>>
>>
>> _______________________________________________
>> 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
>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/df4f6b1c/attachment-0001.html 

From gunther.klein at f24.com  Mon Jan 11 07:51:30 2016
From: gunther.klein at f24.com (gklein)
Date: Mon, 11 Jan 2016 05:51:30 -0700 (MST)
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
Message-ID: <1452516690190-419.post@n5.nabble.com>

Aerogear UPS 1.1.0 collects outdated push message infos in a batch job (calls
PushMessageMetricsService#deleteOutdatedPushInformationData). The outdated
criteria is currently hardcoded to 30 days. 

Feature request: It would be nice to have this time configurable. E.g. when
sending out a lot of pushes over time the db can get quite big (the message
payloads are persisted). We do not need all those information (is contained
in our logs anyways) and it would be ok to have push message info deleted
e.g. after 5 days.

Regards, Gunther Klein



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From nmartin at appstud.me  Mon Jan 11 07:58:00 2016
From: nmartin at appstud.me (Nataniel Martin)
Date: Mon, 11 Jan 2016 12:58:00 +0000
Subject: [Aerogear-users] Compile with latest Cocoapods
In-Reply-To: <CAL8vO=fgjBbm1d3E4iDxGSmRFyEp3jVxa3iCwEVMfu6G_uhxFw@mail.gmail.com>
References: <D917F2AF-82CA-436E-9226-B082A6C14746@appstud.me>
	<CAL8vO=eM=dfMkMmF6F_DcFhD9PR2eFKVeZihv-ubjE0a1OLJUg@mail.gmail.com>
	<CAL8vO=dix6Dp7WHtMF5AD8AF41LHQPA_fO1D=9hXqJiJ6BGo-A@mail.gmail.com>
	<D97588E2-9510-4A86-AC3E-71FC53351BF4@appstud.me>
	<CAL8vO=c3STC5bQPA2bDS9c5zQFZe8NM3BEPpxBQBiS8otJfEOg@mail.gmail.com>
	<BABE0B17-46EF-4389-B66A-A918C1DF6A13@appstud.me>
	<CAL8vO=f22SHrW65=XC0GkTDuk2Db=2PsfKR1VYRGwVfq9Ra5pA@mail.gmail.com>
	<23F31752-A1BE-434B-9DD5-82FE9263CE72@appstud.me>
	<CAL8vO=dopcJ0P-RPksZeb_rh8DpR_GkrW2dKNVcTUGnNqNvZ+w@mail.gmail.com>
	<007DA573-6BB9-4CD2-8231-A88BE6DEF7C1@appstud.me>
	<C5E488EF-4AFE-4C39-8102-C91A81235F9A@appstud.me>
	<8919F509-2BAA-468D-B5B7-DEC345B20221@appstud.me>
	<CAL8vO=d0=PCUeeWYYmD5qmJM0tb5c0sdDt1NumsZDKCtZ51VSQ@mail.gmail.com>
	<097DABD6-45E4-46E3-809E-CEB983218A44@appstud.me>
	<CAL8vO=fgjBbm1d3E4iDxGSmRFyEp3jVxa3iCwEVMfu6G_uhxFw@mail.gmail.com>
Message-ID: <4CA4A18A-6808-4C41-A9B8-EF61301CA0FD@appstud.me>

Hi !

That did the trick:

- Alright after cleaning the derivedData folder
- Clean Build Folder
- Clean
- Modified ONLY_ACTIVE_ARCH to yes
- Make sur that i changed the imports in ViewController.swift:

import AeroGearSyncClientJsonPatch
import AeroGearSyncJsonPatch

??

It compiled and started the app on simulator.

Thanks for the help !

I will work with that for now.

Looking forward the next update on cocoapods ;)

Till then, thanks and have good day !

On 11 Jan 2016, at 16:40, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi Nataniel

I did the same steps you described to solve the last issue, go to AeroGeatSyncDemo target, select build settings and set:
ONLY_ACTIVE_ARCH = YES;
Then delete do a clean build (delete DerivedData)

Let me know how it goes for you. I'll issue a PR on Jedi cookbook.

++
Corinne

On 11 January 2016 at 12:51, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi Corrinne,

Thanks you very much for your help !

So this is what it came out with my testings:

1) First the Podfile used a private library: for KiteValidator;
So in order to work that out, had to slightly modify the Podfile like this :
pod 'KiteJSONValidator', :git => 'https://github.com<https://github.com/>/corinnekrych/KiteJSONValidator.git', :branch => 'podspec.public.header'


2) The import in ViewController.swift from the project : aerogear-ios-cookbook/Jedi/JsonPatchSync

import AeroGearSync
import AeroGearSyncClient

Had to be changed like this:

import AeroGearSyncJsonPatch
import AeroGearSyncClientJsonPatch

3) Now i?m facing a other problem :

private var syncClient: SyncClient<JsonPatchSynchronizer, InMemoryDataStore<JsonNode, JsonPatchEdit>>

SyncClient type is unrecognised by the Xcode (even after a build clean)

-----

This were i?m blocked. But i feel that we are not that far from the solution :)

Let me know if I did something wrong along my explanation.

Best regards !

Nataniel

On 11 Jan 2016, at 14:28, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

I use Xcode 7.2, cocoapods 0.39.0 like you and I faced the same issue.

To sort out the issue, I've defined a new podspec for the ObjC dependencies JSONTools and KiteValidator. Mainly, I rework the import statement and define a modulemap for both libraries.

As we don't directly own the libs I'll issue a PR and start the discussion. Once it's merged we can do a new cocoapods release. In the mean time, you can try it with these fork/branch, in your Podfile, try [1]. Let me know how it goes for you.

++
Corinne.
[1] https://github.com/corinnekrych/aerogear-ios-cookbook-1/blob/8cea70682c2e57028100405fca1171343b07b5be/Jedi/JsonPatchSync/Podfile#L7-L10

On 11 January 2016 at 09:42, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
By the way Corrinne,

What version of Xcode / SWIFT are you using ?

FYI I?m using Xcode 7.2 + Swift 2.1.

Seems that flags are not correctly set.

Best regards,

Nataniel

On 11 Jan 2016, at 11:54, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi !

Any news on these errors ?

I tried a few things on it, but I can?t make it compile :(

Looking forward reading to reading from you.

Nataniel.

On 08 Jan 2016, at 15:02, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:

Hi,

It?s seems to be better that way !

It would like to point you out that with this workaround, even with the Jedi Demo project, there are two errors while building the project:

<Screen Shot 2016-01-08 at 14.52.05.png>

It seems that the import of JSONTools file is not correctly bridged for AeroGearSyncJsonPatch.

Best regards,

Nataniel

On 08 Jan 2016, at 12:44, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi Nataniel

Sorry my bad the pod on master are expressed slightly different (no subpod anymore) see correct syntax [1]. Replace AeroGearSyncClient by  AeroGearSyncClientJsonPatch.
This is a workaround until i do proper release.
++
Corinne
[1] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 09:15, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
The cocoa pod version is:
0.39.0

It?s the latest, not the last beta version that is 1.0.0.beta.2

Regards,
Nataniel

On 08 Jan 2016, at 12:10, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Which cocoapods version are you on?
++
Corinne

On 8 January 2016 at 09:08, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,

Thanks for the swift reply :)

Looking forward for the new version !

But using the exemple in [2] such as:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient', :git => 'https://github.com/aerogear/aerogear-ios-sync-client'

Still give me some errors like these:

Analyzing dependencies
Pre-downloading: `AeroGearSyncClient` from `https://github.com/aerogear/aerogear-ios-sync-client`<https://github.com/aerogear/aerogear-ios-sync-client>
[!] Unable to find a specification for 'AeroGearSyncClient'.

I think the problem is related when you lint the pod.

Best regards !

On 08 Jan 2016, at 12:01, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hi

Looking into aerogear-ios-sync-client release it seems 1.0.0-alpha.3 (which update to Swift 2 syntax) did not make it to cocoapods although we did have a tag for it [1].
1.0.0-alpha.2 (the latest on cocoapods is still on Swift 1.2 syntax).
I'm going to release 1.0.0-alpha.3 shortly in the meantime (as a work around), please us the latest git master version as shown [2].

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/tree/1.0.0-alpha.3
[2] https://github.com/aerogear/aerogear-ios-cookbook/blob/master/Jedi/JsonPatchSync/Podfile#L7

On 8 January 2016 at 08:39, Nataniel Martin <nmartin at appstud.me<mailto:nmartin at appstud.me>> wrote:
Hi,
Thanks for your response.

It?s still not working with this configuration:

PODFILE:

source 'https://github.com/CocoaPods/Specs.git'

platform :ios, '8.0'
platform :ios, :deployment_target => '8.0'
xcodeproj 'TestAerogear.xcodeproj'
use_frameworks!

pod 'AeroGearSyncClient'
pod 'Starscream', '~> 1.0?

?

POD INSTALL:

CocoaPods 1.0.0.beta.2 is available.
To update use: `gem install cocoapods --pre`
[!] This is a test version we'd love you to try.

For more information see http://blog.cocoapods.org<http://blog.cocoapods.org/>
and the CHANGELOG for this version http://git.io/BaH8pQ.

Analyzing dependencies
[!] Unable to satisfy the following requirements:

- `Starscream (~> 1.0)` required by `Podfile`
- `Starscream (= 0.9.3)` required by `Podfile.lock`

Specs satisfying the `Starscream (= 0.9.3)` dependency were found, but they required a higher minimum deployment target.

On 07 Jan 2016, at 17:34, Corinne Krych <corinnekrych at gmail.com<mailto:corinnekrych at gmail.com>> wrote:

Hello Nataniel,

By the look of the errors it seems the Swift syntax of starscream is not using Swift 2. This is hinted by the error on 'join' (Swift1.0 syntax) whereas joinWithSeparator() is Swift 2 syntax).
In Podfile[1] check you're pointing to starscream 1.0.2+ or latest version on master. Previous version of the lib used Swift 1 syntax.

++
Corinne
[1] https://github.com/aerogear/aerogear-ios-sync-client/blob/master/Podfile#L8

_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users


_______________________________________________
Aerogear-users mailing list
Aerogear-users at lists.jboss.org<mailto:Aerogear-users at lists.jboss.org>
https://lists.jboss.org/mailman/listinfo/aerogear-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/23c89ff7/attachment-0001.html 

From lholmqui at redhat.com  Mon Jan 11 09:20:12 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 11 Jan 2016 09:20:12 -0500
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
In-Reply-To: <1452516690190-419.post@n5.nabble.com>
References: <1452516690190-419.post@n5.nabble.com>
Message-ID: <CALD3Fd2oN83YaMKo=gmxzwQmjgpRRMrpi-qxUK325OO506SNvA@mail.gmail.com>

i'd imagine this could be possible in the UI.

perhaps even the ability to purge at will.

are you able to create a JIRA at https://issues.jboss.org/browse/AGPUSH/

if not, i can do it

On Mon, Jan 11, 2016 at 7:51 AM, gklein <gunther.klein at f24.com> wrote:

> Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
> (calls
> PushMessageMetricsService#deleteOutdatedPushInformationData). The outdated
> criteria is currently hardcoded to 30 days.
>
> Feature request: It would be nice to have this time configurable. E.g. when
> sending out a lot of pushes over time the db can get quite big (the message
> payloads are persisted). We do not need all those information (is contained
> in our logs anyways) and it would be ok to have push message info deleted
> e.g. after 5 days.
>
> Regards, Gunther Klein
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/5cb04f34/attachment.html 

From matzew at apache.org  Mon Jan 11 09:22:45 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Mon, 11 Jan 2016 15:22:45 +0100
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
In-Reply-To: <1452516690190-419.post@n5.nabble.com>
References: <1452516690190-419.post@n5.nabble.com>
Message-ID: <CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>

Hi Gunther,

for starters, we csn do a system propterty. Later on, we can have it on the
ui.

Is that ok?

PS: can you file a JIRA for that?



On Monday, 11 January 2016, gklein <gunther.klein at f24.com> wrote:

> Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
> (calls
> PushMessageMetricsService#deleteOutdatedPushInformationData). The outdated
> criteria is currently hardcoded to 30 days.
>
> Feature request: It would be nice to have this time configurable. E.g. when
> sending out a lot of pushes over time the db can get quite big (the message
> payloads are persisted). We do not need all those information (is contained
> in our logs anyways) and it would be ok to have push message info deleted
> e.g. after 5 days.
>
> Regards, Gunther Klein
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org <javascript:;>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/a6ab7df0/attachment.html 

From lholmqui at redhat.com  Mon Jan 11 09:29:14 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Mon, 11 Jan 2016 09:29:14 -0500
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
In-Reply-To: <CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>
References: <1452516690190-419.post@n5.nabble.com>
	<CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>
Message-ID: <CALD3Fd1AZnNo0B_JhtvMuiUbWj=M2XZjJjFkre=nZp8WRe99AQ@mail.gmail.com>

On Mon, Jan 11, 2016 at 9:22 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Gunther,
>
> for starters, we csn do a system propterty. Later on, we can have it on
> the ui.
>
> Is that ok?
>
> PS: can you file a JIRA for that?
>
lol,  we are thinking the same thing.  looks like you missed my email  ;)

>
>
>
>
> On Monday, 11 January 2016, gklein <gunther.klein at f24.com> wrote:
>
>> Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
>> (calls
>> PushMessageMetricsService#deleteOutdatedPushInformationData). The outdated
>> criteria is currently hardcoded to 30 days.
>>
>> Feature request: It would be nice to have this time configurable. E.g.
>> when
>> sending out a lot of pushes over time the db can get quite big (the
>> message
>> payloads are persisted). We do not need all those information (is
>> contained
>> in our logs anyways) and it would be ok to have push message info deleted
>> e.g. after 5 days.
>>
>> Regards, Gunther Klein
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160111/497d4851/attachment.html 

From eug.bab at gmail.com  Mon Jan 11 12:50:36 2016
From: eug.bab at gmail.com (eugeneb)
Date: Mon, 11 Jan 2016 10:50:36 -0700 (MST)
Subject: [Aerogear-users] Android sound and vibrate
In-Reply-To: <CAO2B-fbdweA54GWYdd0jS-pc=ssVyTF=zh7jX5ENRY3jEknfcg@mail.gmail.com>
References: <1452225405997-403.post@n5.nabble.com>
	<CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>
	<1452263436154-412.post@n5.nabble.com>
	<CAO2B-fbdweA54GWYdd0jS-pc=ssVyTF=zh7jX5ENRY3jEknfcg@mail.gmail.com>
Message-ID: <1452534636545-424.post@n5.nabble.com>

Thanks Erik!
So you recommend to adjust the Java code?
Is any way to make this from js when init the plugin?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403p424.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From gunther.klein at f24.com  Tue Jan 12 04:20:23 2016
From: gunther.klein at f24.com (gklein)
Date: Tue, 12 Jan 2016 02:20:23 -0700 (MST)
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
In-Reply-To: <CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>
References: <1452516690190-419.post@n5.nabble.com>
	<CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>
Message-ID: <1452590423299-425.post@n5.nabble.com>

Hi!

Thanks for your replies. I think a system property would be perferrable and
sufficient in our case. Additional ui support is nice to have.

Can you file the jira ticket for me please. I would have to sign up first.
Here is the description:
----

Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
(calls to PushMessageMetricsService#deleteOutdatedPushInformationData). The
outdated criteria is currently hardcoded to 30 days
(PushMessageMetricsService#DAYS_OF_MAX_OLDEST_INFO_MSG). This time should be
made configurable via system property. If the system property is not set the
default value (30 days) should be used.

---

Regards, Gunther Klein



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419p425.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From matzew at apache.org  Tue Jan 12 04:54:56 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Tue, 12 Jan 2016 10:54:56 +0100
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
In-Reply-To: <1452590423299-425.post@n5.nabble.com>
References: <1452516690190-419.post@n5.nabble.com>
	<CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>
	<1452590423299-425.post@n5.nabble.com>
Message-ID: <CAAg5f2R2PYNxz1xf6T0ZXTiC6ss23eU6WApdiEZA351f+ffHqA@mail.gmail.com>

cool, will do.

PR will come soon ;)

On Tuesday, 12 January 2016, gklein <gunther.klein at f24.com> wrote:

> Hi!
>
> Thanks for your replies. I think a system property would be perferrable and
> sufficient in our case. Additional ui support is nice to have.
>
> Can you file the jira ticket for me please. I would have to sign up first.
> Here is the description:
> ----
>
> Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
> (calls to PushMessageMetricsService#deleteOutdatedPushInformationData). The
> outdated criteria is currently hardcoded to 30 days
> (PushMessageMetricsService#DAYS_OF_MAX_OLDEST_INFO_MSG). This time should
> be
> made configurable via system property. If the system property is not set
> the
> default value (30 days) should be used.
>
> ---
>
> Regards, Gunther Klein
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419p425.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org <javascript:;>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>


-- 
Sent from Gmail Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160112/00ff49bc/attachment.html 

From edewit at redhat.com  Tue Jan 12 04:59:02 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 12 Jan 2016 10:59:02 +0100
Subject: [Aerogear-users] Android sound and vibrate
In-Reply-To: <1452534636545-424.post@n5.nabble.com>
References: <1452225405997-403.post@n5.nabble.com>
	<CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>
	<1452263436154-412.post@n5.nabble.com>
	<CAO2B-fbdweA54GWYdd0jS-pc=ssVyTF=zh7jX5ENRY3jEknfcg@mail.gmail.com>
	<1452534636545-424.post@n5.nabble.com>
Message-ID: <CAO2B-fb+QVmwiy78uOApaF_rK56evAKHedhd3Pf91KW37ELiHg@mail.gmail.com>

Hi,

So you recommend to adjust the Java code?
>

Yeah, that would be the quick way for you to continue working


> Is any way to make this from js when init the plugin?
>

Yep, that would be the long term solution, I've created this jira for it
AGCORDOVA-131 [1]

[1] https://issues.jboss.org/browse/AGCORDOVA-131


>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403p424.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160112/e50748cf/attachment-0001.html 

From eug.bab at gmail.com  Tue Jan 12 13:47:37 2016
From: eug.bab at gmail.com (eugeneb)
Date: Tue, 12 Jan 2016 11:47:37 -0700 (MST)
Subject: [Aerogear-users] Android sound and vibrate
In-Reply-To: <CAO2B-fb+QVmwiy78uOApaF_rK56evAKHedhd3Pf91KW37ELiHg@mail.gmail.com>
References: <1452225405997-403.post@n5.nabble.com>
	<CAO2B-fZXQUVzAkdA4+WHNBg5NWKA-i4i6X_0qOBvMms5bpTGAQ@mail.gmail.com>
	<1452263436154-412.post@n5.nabble.com>
	<CAO2B-fbdweA54GWYdd0jS-pc=ssVyTF=zh7jX5ENRY3jEknfcg@mail.gmail.com>
	<1452534636545-424.post@n5.nabble.com>
	<CAO2B-fb+QVmwiy78uOApaF_rK56evAKHedhd3Pf91KW37ELiHg@mail.gmail.com>
Message-ID: <1452624457328-428.post@n5.nabble.com>

Hi Erik,
it would be great help to have this control!

Thanks again!



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Android-sound-and-vibrate-tp403p428.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From edewit at redhat.com  Wed Jan 13 04:43:41 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 13 Jan 2016 10:43:41 +0100
Subject: [Aerogear-users] Possible bug in Aerogear Push Cordova/iOS
 implementation but not in the Cordova/Android version
In-Reply-To: <572042FF-7B4C-4CD0-BC4D-A7057A39A191@robertwillett.com>
References: <CED32543-0A98-4EBF-9945-2EBEF7184271@robertwillett.com>
	<CAO2B-fZCqFV+gtSFHaMWs7oErxSwWwmRN9kKHVW8BLWNW0JiMQ@mail.gmail.com>
	<DF12AFF8-A203-4793-85B6-E5D5A411630F@robertwillett.com>
	<CAD_dpu3og=UaA-OOwKBibT=ea4GC1sWMpoYXhWbXieKpXMUG7Q@mail.gmail.com>
	<783F9E55-54CC-4C9E-857F-64A03DB1BC96@robertwillett.com>
	<CAO2B-fbLaN9hhMPtErXkf0mwb5=K2z23DoP69sOu5p0RWW2VQw@mail.gmail.com>
	<23B53EED-5498-4209-A3D3-D6EB9F221B2A@robertwillett.com>
	<E9382606-BFC9-4788-BC60-B9527010D405@robertwillett.com>
	<572042FF-7B4C-4CD0-BC4D-A7057A39A191@robertwillett.com>
Message-ID: <CAO2B-fYPFoaz+AmyBfO89+tCpiyT5b6SgyN0eGkQmkAXkNkdsw@mail.gmail.com>

Seems to be an cordova issue, when loading a lot of javascript makes the
plugin skip init, are there warnings in the log about this?

On Sun, Dec 20, 2015 at 8:52 PM, Rob Willett <rob.aerogear at robertwillett.com
> wrote:

> Dear all,
>
> We *think* we can now reproduce the problem. Clearly writing the last
> e-mail has focussed our attention :)
>
> Summary.
>
> We have a simple Ionic app that would call the Aerogear notification
> handler when notifications were receive in the foreground and when the app
> was in the background. The Aerogear notification handler would sometimes be
> called and sometimes NOT be called when a notification was received when
> the app was not started. See our long previous e-mails detailing the
> problem.
>
> We think we can now reproduce the problem as follows:
>
>    1.
>
>    Kill the app.
>    2.
>
>    Send a notification down to the app.
>    3.
>
>    It appears in the iOS notification drawer
>    4.
>
>    Click on the notification. if the Aerogear handler has worked then go
>    to 1 and repeat. We want a failure :)
>    5.
>
>    If the Aerogear handler is NOT called, then put the app into the
>    background using the Home button and then click on the app icon to resume.
>    6.
>
>    The notification is now processed by the Aerogear handler. We can now
>    see it.
>
> We are at a loss to explain this, we found it by accident, but we think it
> shows some sort of timing issue somewhere because if we pull out the
> various Javascript files the Aerogear plugin seems to work consistently at
> startup. We have checked and checked the JavaScript files and cannot see
> any error with them at all at load time.
>
> All suggestions welcome now.
>
> Rob
>
> On 20 Dec 2015, at 19:26, Rob Willett wrote:
>
> Erik, Sebastien,
>
> We?ve spent a significant part of the weekend looking into this issue and
> we have still not got to the bottom of it.
>
> We have built a very simple Ionic test app that works in isolation. We
> have used the default Ionic tabs at
>
> http://ionicframework.com/getting-started/
>
> We then add in our Javascript files as <script> entries in the index.html
> file (shown for example)
>
>  <script src="js/polygon.js"></script>
>  <script src="js/urls.js"></script>
>  <script src="js/utilities.js"></script>
>
>  <script src="js/moment.js"></script>
>  <script src="js/perimeter.js"></script>
>  <script src="js/leaflet.markercluster-src.js"></script>
>  <script src="js/cycle.js"></script>
>  <script src="js/clipper.js"></script>
>  <script src="js/easy_button.js"></script>
>  <script src="js/graham_scan.js"></script>
>  <script src="js/sha.js"></script>
>  <script src="js/r-tree.js"></script>
>  <script src="js/angular-leaflet-directive.min.js"></script>
>  <script src="pouchdb/L.TileLayer.PouchDBCached.js"></script>
>  <script src="pouchdb/pouchdb-5.1.0.min.js"></script>
>
> We do NOT call any functions within any of these files, indeed we make no
> reference to these files beyond including them in the index.html file. Our
> dummy html templates make no reference to them. We simply load the
> javascript files in. We get no errors from including the files. We have
> used the controllers and services as provided by the dummy sample Ionic app.
>
> If we then send foreground notifications, the notifications are always
> handled by the Aerogear notification handler.
>
> If we send notifications to the app when it is in the background, the
> notifications are always handled by the Aerogear notification handler.
>
> If we kill by swiping up the app, we get the notifications but when we
> click on the notification from the main IOS screen it is arbitrary as to
> whether the notification is handled by the Aerogear handler when the app
> starts up. Sometimes the handler is called, but once the handler is not
> called, the Aerogear notification handler never appears to be called again.
> If we reinstall the app it sometimes works again and sometimes it fails.
>
> We can reinstall the app and the Aerogear notification handler might be
> called or it might not. We just ran the app with 20 tests to the app, each
> time killing the app and then sending down a a notification and it started
> the Aerogear notification handler each time. We then reinstall the app
> again, no changes in the code and it simply doesn?t process any
> notification when the app is closed. The notification turns up, but no
> event is called to the Aerogear event handler.
>
> Given that we are getting arbitrary results from the same codebase,
> clearly something is remiss. Sometimes it works and sometimes it doesn?t.
> There is no logic that we can see. We?ve closed down Xcode after
> installing, we?ve started and stopped our sample app a few times to try and
> make sure its closed down, ew are sending exactly the same payload each
> time.
>
> We feel that there is some sort of timing or race condition, or if this
> was a piece of C code, that we are overwriting somewhere we shouldn?t be.
> It has that sort of feeling of a pointer going bad but we cannot see where
> the issue is at all. The fact that we get different results from doing the
> same install is very worrying but we can?t say whether its the Aerogear
> plugin, Ionic or our code.
>
> Thanks,
>
> Rob
>
> On 18 Dec 2015, at 17:26, Rob Willett wrote:
>
> Erok,
>
> We?ve not forgotten the notification issue, we?re still working on it to
> try and get to the bottom of it. The problem for us is that its not so
> simple to cut code out and try and reduce the problem down. Our code is
> quite interlinked, for good or for worse.
>
> We?ve added some simple sound debugging to the Objective C source for the
> Aerogear plugin. This means that we can hear where things are when the
> plugin starts up from a cold start after receiving a notification. This
> works quite well.
>
> We initially added a beep to here
>
> - (void)notificationReceived {
> NSLog(@"Notification received");
>
> AudioServicesPlaySystemSound(1005);
>
>
> if (notificationMessage && self.callbackId) {
>
> and this works whenever we get a notification in the foreground and when
> the app is in the background. We then started tracing backwards in the
> source code to see what called notificationReceived
>
> We can see it here
>
> - (void)register:(CDVInvokedUrlCommand *)command; {
> NSLog(@"register");
> self.callbackId = command.callbackId;
>
> AudioServicesPlaySystemSound(1007);
>
> isInline = NO;
>
> [self.commandDelegate runInBackground:^{
>  NSMutableDictionary *options = [self parseOptions:command];
>  [self saveConfig:options];
>
>  // when running under iOS 8 we will use the new API for APNS registration
>  #if __IPHONE_OS_VERSION_MAX_ALLOWED >= 80000
>      if ([[UIApplication sharedApplication] respondsToSelector:@selector(registerUserNotificationSettings:)]) {
>          UIUserNotificationSettings* notificationSettings = [UIUserNotificationSettings settingsForTypes:UIUserNotificationTypeAlert | UIUserNotificationTypeBadge | UIUserNotificationTypeSound categories:nil];
>          [[UIApplication sharedApplication] registerUserNotificationSettings:notificationSettings];
>          [[UIApplication sharedApplication] registerForRemoteNotifications];
>      } else {
>          [[UIApplication sharedApplication] registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>      }
>
>  #else
>      [[UIApplication sharedApplication] registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge | UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>  #endif
>
>  CDVPluginResult* pluginResult = [CDVPluginResult resultWithStatus:CDVCommandStatus_NO_RESULT];
>  [pluginResult setKeepCallback:@YES];
>  [self.commandDelegate sendPluginResult:pluginResult callbackId:command.callbackId];
> }];
>
> if (notificationMessage)            // if there is a pending startup notification
> {
>  AudioServicesPlaySystemSound(1024);
>
>  [self notificationReceived];    // go ahead and process it
> }
> }
>
> So we add some more beeps in to track down whats going on. We add
> AudioServicesPlaySystemSound(1007) at the beginning of the function and add
> AudioServicesPlaySystemSound(1024) just before we call the
> notificationReceived method.
>
> We get the first sounds on startup but do NOT get the second set of
> sounds. It looks like notificationMessage is not being set at application
> startup.
>
> Our problem now is that we are not Objective-C developers so we are
> struggling to debug much further. So trying to understand how
> notificationMessage is set and defined as its declared as @synthesis is
> unclear. We?ll start reading and learning quickly but as this is new for
> us, so we will be slow.
>
> Any suggestions welcomed,
>
> Rob
>
> On 16 Dec 2015, at 16:54, Erik Jan de Wit wrote:
>
> Hi Rob,
>
> What you could try is to debug this in xcode, when the notification is
> touched it should launch the app and that will in turn call the JS
> callback. Would be good to see if this code is called 100% of the time.
>
> You can put a breakpoint here:
>
> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AppDelegate%2Bnotification.m#L56
>
> That code will execute on cold start and here:
>
> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AGPushPlugin.m#L102
>
> That is where the onNotification callback gets invoked.
>
> Hope this helps,
>
> On Wed, Dec 16, 2015 at 5:14 PM, Rob Willett <
> rob.aerogear at robertwillett.com
>
> wrote:
>
> Sebastien
>
> Yes, we do it at that point, $ionicPlatform.ready. I include the whole of
> that area of code for reference but we?re not expecting you to debug it for
> us. Merely to demonstrate its there.
>
> At the moment all we want the code to do is put an alert up.
>
> .run(function($ionicPlatform , CordovaService) {
> $ionicPlatform.ready(function() {
> if (window.StatusBar) {
> // org.apache.cordova.statusbar required
> StatusBar.styleDefault();
> }
>
> ConsoleLog('<<< Cordova ready >>>');
>
> /* This seems to remove an annoying page flicker on iOS when the keyboard
> is displayed */
> cordova.plugins.Keyboard.disableScroll(true);
>
> isDeviceReady = true;
>
> var uuid = "D26FBAF1-2EF2-4614-875F-4497EC4212D5/JFL1-0/ios_app";
>
> var aeroGearPushConfig = {
> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
> ios: {
> variantID: ?XXXXX?,
> variantSecret: ?YYYYYYY?
> } ,
> // sendMetricInfo: true,
> alias: uuid
> };
>
> push.register(function (event) {
> alert("EVENT = " + JSON.stringify(event));
>
> } , function () {
> if (1)
> {
> // alert("AeroGearSuccessHandler: OK " + JSON.stringify(uuid));
> // ConsoleLog("UUID = " + uuid);
> }
> } , function () {
> } , aeroGearPushConfig);
>
> We were still loading up another 18,000 lines of code so we need to start
> pruning that back until we have something that works.
>
> Rob
>
> On 16 Dec 2015, at 16:04, Sebastien Blanc wrote:
>
> In the ionic app when do you do the registration of UPS ? on the
> platformReady event ?
>
> On Wed, Dec 16, 2015 at 4:54 PM, Rob Willett <
> rob.aerogear at robertwillett.com
>
> wrote:
>
> Erik,
>
> We have built the simplest possible app we can that uses the Aerogear
> push plugin but using the ionic tabs starter kit.
>
> http://ionicframework.com/getting-started/
>
> We have taken the code directly from the Cordova simple app that we have
> got working and put it into the Ionic app.
>
> if we follow your tests as below:
>
> 1.
>
> IOS App in foreground, we send a simple push notification from the
> Aerogear console - Works OK, We can see the event. Good
> 2.
>
> IOS App in background, we send a simple push notification from the
> Aerogear console - Works OK, We can see the event. Good
> 3.
>
> IOS App killed, we send a simple push notification from the Aerogear
>
> console and some of the time when we click on the notification in the
> notification drawer we do NOT get the notification handler called. Not
> so good
>
> However it does appear to work most of the time with our minimal Ionic
> app, but some of the time it fails. We had a run of 1 in 2 failures when
> we click on the notification. Now we have just done 20 runs in a row,
> each time killing the app after receiving the notification and not a
> single failure. Nothing changed.
>
> We cannot find any obvious reason for this so we are still
> investigating.
>
> We have reconfigured our main app to work the same way as the minimal
> app but we are still getting the same issues as before, we can see the
> notification in the drawer but clicking on it does NOT call the same
> handler with the same code as the minimal app. We get zero calls to the
> notification event handler.
>
> We are wondering if there is a timing issue somewhere in our code, but
> we can?t see it. We also wondered if the size of the code we are
> loading is the cause of a timing issue as well.
>
> Is there any way of adding more debugging into the Aerogear push plugin
> to see if we can track things down that way?
>
> Its very frustrating, but thanks for your help to date. It does look
> like its an interaction with our code, Ionic and the Aerogear plugin. My
> money is on our code though. We?ll now start pulling working code out
> of our app until we get back to the minimal app. Only 18,604 lines to go
> :)
>
> Rob
>
> On 15 Dec 2015, at 10:36, Erik Jan de Wit wrote:
>
> Hi Rob,
>
> That would be a bug, although I can not reproduce it, to test it this
> is
> what I've done to test it:
> $ > cordova create push-test <my bundle id>
> $ > cordova platform add ios
> $ > cordova plugin add aerogear-cordova-push
>
> copy paste your js code into www/js/index.js onDeviceReady, changed
> pushServerUrl and variant info and changed quotes to " (this is your
> email
> client no doubt) and changed : into ; after console.log("Success")
>
> Attach Safari debugger and send a message when the app is in the
> foreground
> and get in the console:
>
> HandleAeroGearNotification: event =>
>
>
> {"alert":"test","foreground":true,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>
> I press the home button and send the app to the background send
> another
> message and 'touch' the message to launch the app:
>
> HandleAeroGearNotification: event =>
>
>
> {"alert":"background","foreground":false,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>
> The I kill the app by pressing home twice and swiping over the app to
> remove it send another message and 'touch' it to launch the app. This
> kills
> my safari debugger so no way to see the console log, but in this case
> coldstart should be true. To test this better changed the code to
> alert
> instead of console:
>
> function HandleAeroGearNotification(event) {
> alert("HandleAeroGearNotification: event => " + event.coldstart);
>
> // Stuff cut for clarity
> }
>
> I send another notification 'touch' it to launch the app and see the
> alert
> box display the text:
>
> HandleAeroGearNotification: event => true
>
> Hope this helps
>
> On Mon, Dec 14, 2015 at 10:20 PM, Rob Willett <
> rob.aerogear at robertwillett.com> wrote:
>
> Hi,
>
> We think we have found a possible bug in the Aerogear Cordova 2.0.4
> push
> plugin specifically on the iOS side.
> Summary
>
> We have two versions of our app, an Android and an IOS version. Both
> use
> the latest Cordova push plugin 2.0.4. They also both have the latest
> Cordova platforms, android 4.1.1, ios 3.9.2. Both the iOS and Android
> versions are compiled at the same time. We are running cordova 5.3.3
> with
> Ionic 1.7.8 (?).
>
> 1.
>
> We make sure that both apps are NOT started up on each device. We
> also
> check they are NOT in the background.
> 2.
>
> We send the same simple notification to each device. This
> notification
> config is as below, we have anonymised the variants and alias in this
> JSON
> structure, though we can report that the UPS server sends the data
> correctly. We use the additionalData flag to provide the information
> necessary to decide which notification has been clicked in the
> notification
> drawer.
>
> 'variants' => [?variant1?,?variant2? ],
> 'message' => {
> 'additionalData' => { 'Disruption_Id' => '107546',
> 'EpochTime' => '1450125268'
> },
> 'alert' => 'Cannon Street (EC4N) (All Directions) at the junction of
> King William Street - To facilitate a heavy lift in Cannon Street,
> Cannon Street will be closed. Traffic is slow moving on diversion.'
> },
> 'alias' => [ ?alias1? ],
> 'ttl' => 600
> };
>
> 1.
>
> Both devices show the message, the Android device stacks the message
> and the iOS device display an individual message. This looks correct.
> 2.
>
> Clicking on the Android stacked message starts up the app and the
> Javascript notification handler we have defined,
> HandleAeroGearNotification
> is called
>
> HandleAeroGearNotification: event => {"alert":"Cannon Street (EC4N)
> (All Directions) at the junction of King William Street - To
> facilitate a heavy lift in Cannon Street, Cannon Street will be
> closed. Traffic is slow moving on
>
> diversion.","coldstart":true,"foreground":true,"payload":{"alert":"Cannon
>
> Street (EC4N) (All Directions) at the junction of King William Street
> - To facilitate a heavy lift in Cannon Street, Cannon Street will be
> closed. Traffic is slow moving on diversion.","badge":"-1"}}
>
> 1.
>
> Clicking on the notification in the notification drawer on the iOS
> device also starts our app up correctly but the notification handler,
> HandleAeroGearNotification(), is NOT called. The app starts up as
> normal as
> if the notification had not been clicked. We would expect the
> notification
> handler to be called in iOS as it is in Android.
> 2.
>
> All notifications are cleared on both Android and iOS correctly when
> the app is started up.
> 3.
>
> We define HandleAeroGearNotification as
>
> var aeroGearPushConfig = {
> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
> ios: {
> variantID: ?variantid_obscured?,
> variantSecret: ?variant_secret_obscured?
> } ,
> android: {
> senderID: "variantid_obscured" ,
> variantID: "variant_id_obscured" ,
> variantSecret: "variant_secret_obscured"
> } ,
> sendMetricInfo: true,
> alias: alias1
> };
>
> function HandleAeroGearNotification(event) {
> console.log(?HandleAeroGearNotification: event => ? +
> JSON.stringify(event));
>
> // Stuff cut for clarity
> }
>
> // Slightly simplified registration event.
> push.register(HandleAeroGearNotification , function () {
> console.log(?Success?):
> } , function () {
> console.log(?Failure?);
> } , aeroGearPushConfig);
>
> We cannot see any reference to this issue in the JIRA database and
> wondered if it is a bug or not.
>
> If its a bug we are happy to raise it accordingly.
>
> Please let us know,
>
> Thanks
> Rob
>
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
> --
> Cheers,
> Erik Jan
>
> 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
> ------------------------------
>
> 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
>
> --
> Cheers,
> Erik Jan
> ------------------------------
>
> 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
>
> ------------------------------
>
> 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
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160113/5cbf6296/attachment-0001.html 

From rob.aerogear at robertwillett.com  Wed Jan 13 06:07:42 2016
From: rob.aerogear at robertwillett.com (Rob Willett)
Date: Wed, 13 Jan 2016 11:07:42 +0000
Subject: [Aerogear-users] Possible bug in Aerogear Push Cordova/iOS
 implementation but not in the Cordova/Android version
In-Reply-To: <CAO2B-fYPFoaz+AmyBfO89+tCpiyT5b6SgyN0eGkQmkAXkNkdsw@mail.gmail.com>
References: <CED32543-0A98-4EBF-9945-2EBEF7184271@robertwillett.com>
	<CAO2B-fZCqFV+gtSFHaMWs7oErxSwWwmRN9kKHVW8BLWNW0JiMQ@mail.gmail.com>
	<DF12AFF8-A203-4793-85B6-E5D5A411630F@robertwillett.com>
	<CAD_dpu3og=UaA-OOwKBibT=ea4GC1sWMpoYXhWbXieKpXMUG7Q@mail.gmail.com>
	<783F9E55-54CC-4C9E-857F-64A03DB1BC96@robertwillett.com>
	<CAO2B-fbLaN9hhMPtErXkf0mwb5=K2z23DoP69sOu5p0RWW2VQw@mail.gmail.com>
	<23B53EED-5498-4209-A3D3-D6EB9F221B2A@robertwillett.com>
	<E9382606-BFC9-4788-BC60-B9527010D405@robertwillett.com>
	<572042FF-7B4C-4CD0-BC4D-A7057A39A191@robertwillett.com>
	<CAO2B-fYPFoaz+AmyBfO89+tCpiyT5b6SgyN0eGkQmkAXkNkdsw@mail.gmail.com>
Message-ID: <3D0FE23F-93F4-4F90-9834-1539B51D9B25@robertwillett.com>

Erik,

No there are no warnings or any any errors. Errors and warnings we can 
work with, this simply didn?t fire.

At the moment we have got around the issue with a different plugin. We 
didn?t change the architecture at all and the different plugin works.

At the time we thought it was a timing or race condition and we still 
think that.

We have this on the backburner as we need to get a release out. We?ll 
try and revisit it later but it won?t be for a few weeks as Twitter 
interfaces, GPS maps and route matching is on the critical path :)

Thanks

Rob

On 13 Jan 2016, at 9:43, Erik Jan de Wit wrote:

> Seems to be an cordova issue, when loading a lot of javascript makes 
> the
> plugin skip init, are there warnings in the log about this?
>
> On Sun, Dec 20, 2015 at 8:52 PM, Rob Willett 
> <rob.aerogear at robertwillett.com
>> wrote:
>
>> Dear all,
>>
>> We *think* we can now reproduce the problem. Clearly writing the last
>> e-mail has focussed our attention :)
>>
>> Summary.
>>
>> We have a simple Ionic app that would call the Aerogear notification
>> handler when notifications were receive in the foreground and when 
>> the app
>> was in the background. The Aerogear notification handler would 
>> sometimes be
>> called and sometimes NOT be called when a notification was received 
>> when
>> the app was not started. See our long previous e-mails detailing the
>> problem.
>>
>> We think we can now reproduce the problem as follows:
>>
>> 1.
>>
>> Kill the app.
>> 2.
>>
>> Send a notification down to the app.
>> 3.
>>
>> It appears in the iOS notification drawer
>> 4.
>>
>> Click on the notification. if the Aerogear handler has worked then go
>> to 1 and repeat. We want a failure :)
>> 5.
>>
>> If the Aerogear handler is NOT called, then put the app into the
>> background using the Home button and then click on the app icon to 
>> resume.
>> 6.
>>
>> The notification is now processed by the Aerogear handler. We can now
>> see it.
>>
>> We are at a loss to explain this, we found it by accident, but we 
>> think it
>> shows some sort of timing issue somewhere because if we pull out the
>> various Javascript files the Aerogear plugin seems to work 
>> consistently at
>> startup. We have checked and checked the JavaScript files and cannot 
>> see
>> any error with them at all at load time.
>>
>> All suggestions welcome now.
>>
>> Rob
>>
>> On 20 Dec 2015, at 19:26, Rob Willett wrote:
>>
>> Erik, Sebastien,
>>
>> We?ve spent a significant part of the weekend looking into this 
>> issue and
>> we have still not got to the bottom of it.
>>
>> We have built a very simple Ionic test app that works in isolation. 
>> We
>> have used the default Ionic tabs at
>>
>> http://ionicframework.com/getting-started/
>>
>> We then add in our Javascript files as <script> entries in the 
>> index.html
>> file (shown for example)
>>
>> <script src="js/polygon.js"></script>
>> <script src="js/urls.js"></script>
>> <script src="js/utilities.js"></script>
>>
>> <script src="js/moment.js"></script>
>> <script src="js/perimeter.js"></script>
>> <script src="js/leaflet.markercluster-src.js"></script>
>> <script src="js/cycle.js"></script>
>> <script src="js/clipper.js"></script>
>> <script src="js/easy_button.js"></script>
>> <script src="js/graham_scan.js"></script>
>> <script src="js/sha.js"></script>
>> <script src="js/r-tree.js"></script>
>> <script src="js/angular-leaflet-directive.min.js"></script>
>> <script src="pouchdb/L.TileLayer.PouchDBCached.js"></script>
>> <script src="pouchdb/pouchdb-5.1.0.min.js"></script>
>>
>> We do NOT call any functions within any of these files, indeed we 
>> make no
>> reference to these files beyond including them in the index.html 
>> file. Our
>> dummy html templates make no reference to them. We simply load the
>> javascript files in. We get no errors from including the files. We 
>> have
>> used the controllers and services as provided by the dummy sample 
>> Ionic app.
>>
>> If we then send foreground notifications, the notifications are 
>> always
>> handled by the Aerogear notification handler.
>>
>> If we send notifications to the app when it is in the background, the
>> notifications are always handled by the Aerogear notification 
>> handler.
>>
>> If we kill by swiping up the app, we get the notifications but when 
>> we
>> click on the notification from the main IOS screen it is arbitrary as 
>> to
>> whether the notification is handled by the Aerogear handler when the 
>> app
>> starts up. Sometimes the handler is called, but once the handler is 
>> not
>> called, the Aerogear notification handler never appears to be called 
>> again.
>> If we reinstall the app it sometimes works again and sometimes it 
>> fails.
>>
>> We can reinstall the app and the Aerogear notification handler might 
>> be
>> called or it might not. We just ran the app with 20 tests to the app, 
>> each
>> time killing the app and then sending down a a notification and it 
>> started
>> the Aerogear notification handler each time. We then reinstall the 
>> app
>> again, no changes in the code and it simply doesn?t process any
>> notification when the app is closed. The notification turns up, but 
>> no
>> event is called to the Aerogear event handler.
>>
>> Given that we are getting arbitrary results from the same codebase,
>> clearly something is remiss. Sometimes it works and sometimes it 
>> doesn?t.
>> There is no logic that we can see. We?ve closed down Xcode after
>> installing, we?ve started and stopped our sample app a few times to 
>> try and
>> make sure its closed down, ew are sending exactly the same payload 
>> each
>> time.
>>
>> We feel that there is some sort of timing or race condition, or if 
>> this
>> was a piece of C code, that we are overwriting somewhere we 
>> shouldn?t be.
>> It has that sort of feeling of a pointer going bad but we cannot see 
>> where
>> the issue is at all. The fact that we get different results from 
>> doing the
>> same install is very worrying but we can?t say whether its the 
>> Aerogear
>> plugin, Ionic or our code.
>>
>> Thanks,
>>
>> Rob
>>
>> On 18 Dec 2015, at 17:26, Rob Willett wrote:
>>
>> Erok,
>>
>> We?ve not forgotten the notification issue, we?re still working 
>> on it to
>> try and get to the bottom of it. The problem for us is that its not 
>> so
>> simple to cut code out and try and reduce the problem down. Our code 
>> is
>> quite interlinked, for good or for worse.
>>
>> We?ve added some simple sound debugging to the Objective C source 
>> for the
>> Aerogear plugin. This means that we can hear where things are when 
>> the
>> plugin starts up from a cold start after receiving a notification. 
>> This
>> works quite well.
>>
>> We initially added a beep to here
>>
>> - (void)notificationReceived {
>> NSLog(@"Notification received");
>>
>> AudioServicesPlaySystemSound(1005);
>>
>>
>> if (notificationMessage && self.callbackId) {
>>
>> and this works whenever we get a notification in the foreground and 
>> when
>> the app is in the background. We then started tracing backwards in 
>> the
>> source code to see what called notificationReceived
>>
>> We can see it here
>>
>> - (void)register:(CDVInvokedUrlCommand *)command; {
>> NSLog(@"register");
>> self.callbackId = command.callbackId;
>>
>> AudioServicesPlaySystemSound(1007);
>>
>> isInline = NO;
>>
>> [self.commandDelegate runInBackground:^{
>> NSMutableDictionary *options = [self parseOptions:command];
>> [self saveConfig:options];
>>
>> // when running under iOS 8 we will use the new API for APNS 
>> registration
>> #if __IPHONE_OS_VERSION_MAX_ALLOWED >= 80000
>>   if ([[UIApplication sharedApplication] 
>> respondsToSelector:@selector(registerUserNotificationSettings:)]) {
>>       UIUserNotificationSettings* notificationSettings = 
>> [UIUserNotificationSettings 
>> settingsForTypes:UIUserNotificationTypeAlert | 
>> UIUserNotificationTypeBadge | UIUserNotificationTypeSound 
>> categories:nil];
>>       [[UIApplication sharedApplication] 
>> registerUserNotificationSettings:notificationSettings];
>>       [[UIApplication sharedApplication] 
>> registerForRemoteNotifications];
>>   } else {
>>       [[UIApplication sharedApplication] 
>> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge | 
>> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>>   }
>>
>> #else
>>   [[UIApplication sharedApplication] 
>> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge | 
>> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>> #endif
>>
>> CDVPluginResult* pluginResult = [CDVPluginResult 
>> resultWithStatus:CDVCommandStatus_NO_RESULT];
>> [pluginResult setKeepCallback:@YES];
>> [self.commandDelegate sendPluginResult:pluginResult 
>> callbackId:command.callbackId];
>> }];
>>
>> if (notificationMessage)            // if there is a pending startup 
>> notification
>> {
>> AudioServicesPlaySystemSound(1024);
>>
>> [self notificationReceived];    // go ahead and process it
>> }
>> }
>>
>> So we add some more beeps in to track down whats going on. We add
>> AudioServicesPlaySystemSound(1007) at the beginning of the function 
>> and add
>> AudioServicesPlaySystemSound(1024) just before we call the
>> notificationReceived method.
>>
>> We get the first sounds on startup but do NOT get the second set of
>> sounds. It looks like notificationMessage is not being set at 
>> application
>> startup.
>>
>> Our problem now is that we are not Objective-C developers so we are
>> struggling to debug much further. So trying to understand how
>> notificationMessage is set and defined as its declared as @synthesis 
>> is
>> unclear. We?ll start reading and learning quickly but as this is 
>> new for
>> us, so we will be slow.
>>
>> Any suggestions welcomed,
>>
>> Rob
>>
>> On 16 Dec 2015, at 16:54, Erik Jan de Wit wrote:
>>
>> Hi Rob,
>>
>> What you could try is to debug this in xcode, when the notification 
>> is
>> touched it should launch the app and that will in turn call the JS
>> callback. Would be good to see if this code is called 100% of the 
>> time.
>>
>> You can put a breakpoint here:
>>
>> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AppDelegate%2Bnotification.m#L56
>>
>> That code will execute on cold start and here:
>>
>> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AGPushPlugin.m#L102
>>
>> That is where the onNotification callback gets invoked.
>>
>> Hope this helps,
>>
>> On Wed, Dec 16, 2015 at 5:14 PM, Rob Willett <
>> rob.aerogear at robertwillett.com
>>
>> wrote:
>>
>> Sebastien
>>
>> Yes, we do it at that point, $ionicPlatform.ready. I include the 
>> whole of
>> that area of code for reference but we?re not expecting you to 
>> debug it for
>> us. Merely to demonstrate its there.
>>
>> At the moment all we want the code to do is put an alert up.
>>
>> .run(function($ionicPlatform , CordovaService) {
>> $ionicPlatform.ready(function() {
>> if (window.StatusBar) {
>> // org.apache.cordova.statusbar required
>> StatusBar.styleDefault();
>> }
>>
>> ConsoleLog('<<< Cordova ready >>>');
>>
>> /* This seems to remove an annoying page flicker on iOS when the 
>> keyboard
>> is displayed */
>> cordova.plugins.Keyboard.disableScroll(true);
>>
>> isDeviceReady = true;
>>
>> var uuid = "D26FBAF1-2EF2-4614-875F-4497EC4212D5/JFL1-0/ios_app";
>>
>> var aeroGearPushConfig = {
>> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>> ios: {
>> variantID: ?XXXXX?,
>> variantSecret: ?YYYYYYY?
>> } ,
>> // sendMetricInfo: true,
>> alias: uuid
>> };
>>
>> push.register(function (event) {
>> alert("EVENT = " + JSON.stringify(event));
>>
>> } , function () {
>> if (1)
>> {
>> // alert("AeroGearSuccessHandler: OK " + JSON.stringify(uuid));
>> // ConsoleLog("UUID = " + uuid);
>> }
>> } , function () {
>> } , aeroGearPushConfig);
>>
>> We were still loading up another 18,000 lines of code so we need to 
>> start
>> pruning that back until we have something that works.
>>
>> Rob
>>
>> On 16 Dec 2015, at 16:04, Sebastien Blanc wrote:
>>
>> In the ionic app when do you do the registration of UPS ? on the
>> platformReady event ?
>>
>> On Wed, Dec 16, 2015 at 4:54 PM, Rob Willett <
>> rob.aerogear at robertwillett.com
>>
>> wrote:
>>
>> Erik,
>>
>> We have built the simplest possible app we can that uses the Aerogear
>> push plugin but using the ionic tabs starter kit.
>>
>> http://ionicframework.com/getting-started/
>>
>> We have taken the code directly from the Cordova simple app that we 
>> have
>> got working and put it into the Ionic app.
>>
>> if we follow your tests as below:
>>
>> 1.
>>
>> IOS App in foreground, we send a simple push notification from the
>> Aerogear console - Works OK, We can see the event. Good
>> 2.
>>
>> IOS App in background, we send a simple push notification from the
>> Aerogear console - Works OK, We can see the event. Good
>> 3.
>>
>> IOS App killed, we send a simple push notification from the Aerogear
>>
>> console and some of the time when we click on the notification in the
>> notification drawer we do NOT get the notification handler called. 
>> Not
>> so good
>>
>> However it does appear to work most of the time with our minimal 
>> Ionic
>> app, but some of the time it fails. We had a run of 1 in 2 failures 
>> when
>> we click on the notification. Now we have just done 20 runs in a row,
>> each time killing the app after receiving the notification and not a
>> single failure. Nothing changed.
>>
>> We cannot find any obvious reason for this so we are still
>> investigating.
>>
>> We have reconfigured our main app to work the same way as the minimal
>> app but we are still getting the same issues as before, we can see 
>> the
>> notification in the drawer but clicking on it does NOT call the same
>> handler with the same code as the minimal app. We get zero calls to 
>> the
>> notification event handler.
>>
>> We are wondering if there is a timing issue somewhere in our code, 
>> but
>> we can?t see it. We also wondered if the size of the code we are
>> loading is the cause of a timing issue as well.
>>
>> Is there any way of adding more debugging into the Aerogear push 
>> plugin
>> to see if we can track things down that way?
>>
>> Its very frustrating, but thanks for your help to date. It does look
>> like its an interaction with our code, Ionic and the Aerogear plugin. 
>> My
>> money is on our code though. We?ll now start pulling working code 
>> out
>> of our app until we get back to the minimal app. Only 18,604 lines to 
>> go
>> :)
>>
>> Rob
>>
>> On 15 Dec 2015, at 10:36, Erik Jan de Wit wrote:
>>
>> Hi Rob,
>>
>> That would be a bug, although I can not reproduce it, to test it this
>> is
>> what I've done to test it:
>> $ > cordova create push-test <my bundle id>
>> $ > cordova platform add ios
>> $ > cordova plugin add aerogear-cordova-push
>>
>> copy paste your js code into www/js/index.js onDeviceReady, changed
>> pushServerUrl and variant info and changed quotes to " (this is your
>> email
>> client no doubt) and changed : into ; after console.log("Success")
>>
>> Attach Safari debugger and send a message when the app is in the
>> foreground
>> and get in the console:
>>
>> HandleAeroGearNotification: event =>
>>
>>
>> {"alert":"test","foreground":true,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>>
>> I press the home button and send the app to the background send
>> another
>> message and 'touch' the message to launch the app:
>>
>> HandleAeroGearNotification: event =>
>>
>>
>> {"alert":"background","foreground":false,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>>
>> The I kill the app by pressing home twice and swiping over the app to
>> remove it send another message and 'touch' it to launch the app. This
>> kills
>> my safari debugger so no way to see the console log, but in this case
>> coldstart should be true. To test this better changed the code to
>> alert
>> instead of console:
>>
>> function HandleAeroGearNotification(event) {
>> alert("HandleAeroGearNotification: event => " + event.coldstart);
>>
>> // Stuff cut for clarity
>> }
>>
>> I send another notification 'touch' it to launch the app and see the
>> alert
>> box display the text:
>>
>> HandleAeroGearNotification: event => true
>>
>> Hope this helps
>>
>> On Mon, Dec 14, 2015 at 10:20 PM, Rob Willett <
>> rob.aerogear at robertwillett.com> wrote:
>>
>> Hi,
>>
>> We think we have found a possible bug in the Aerogear Cordova 2.0.4
>> push
>> plugin specifically on the iOS side.
>> Summary
>>
>> We have two versions of our app, an Android and an IOS version. Both
>> use
>> the latest Cordova push plugin 2.0.4. They also both have the latest
>> Cordova platforms, android 4.1.1, ios 3.9.2. Both the iOS and Android
>> versions are compiled at the same time. We are running cordova 5.3.3
>> with
>> Ionic 1.7.8 (?).
>>
>> 1.
>>
>> We make sure that both apps are NOT started up on each device. We
>> also
>> check they are NOT in the background.
>> 2.
>>
>> We send the same simple notification to each device. This
>> notification
>> config is as below, we have anonymised the variants and alias in this
>> JSON
>> structure, though we can report that the UPS server sends the data
>> correctly. We use the additionalData flag to provide the information
>> necessary to decide which notification has been clicked in the
>> notification
>> drawer.
>>
>> 'variants' => [?variant1?,?variant2? ],
>> 'message' => {
>> 'additionalData' => { 'Disruption_Id' => '107546',
>> 'EpochTime' => '1450125268'
>> },
>> 'alert' => 'Cannon Street (EC4N) (All Directions) at the junction of
>> King William Street - To facilitate a heavy lift in Cannon Street,
>> Cannon Street will be closed. Traffic is slow moving on diversion.'
>> },
>> 'alias' => [ ?alias1? ],
>> 'ttl' => 600
>> };
>>
>> 1.
>>
>> Both devices show the message, the Android device stacks the message
>> and the iOS device display an individual message. This looks correct.
>> 2.
>>
>> Clicking on the Android stacked message starts up the app and the
>> Javascript notification handler we have defined,
>> HandleAeroGearNotification
>> is called
>>
>> HandleAeroGearNotification: event => {"alert":"Cannon Street (EC4N)
>> (All Directions) at the junction of King William Street - To
>> facilitate a heavy lift in Cannon Street, Cannon Street will be
>> closed. Traffic is slow moving on
>>
>> diversion.","coldstart":true,"foreground":true,"payload":{"alert":"Cannon
>>
>> Street (EC4N) (All Directions) at the junction of King William Street
>> - To facilitate a heavy lift in Cannon Street, Cannon Street will be
>> closed. Traffic is slow moving on diversion.","badge":"-1"}}
>>
>> 1.
>>
>> Clicking on the notification in the notification drawer on the iOS
>> device also starts our app up correctly but the notification handler,
>> HandleAeroGearNotification(), is NOT called. The app starts up as
>> normal as
>> if the notification had not been clicked. We would expect the
>> notification
>> handler to be called in iOS as it is in Android.
>> 2.
>>
>> All notifications are cleared on both Android and iOS correctly when
>> the app is started up.
>> 3.
>>
>> We define HandleAeroGearNotification as
>>
>> var aeroGearPushConfig = {
>> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>> ios: {
>> variantID: ?variantid_obscured?,
>> variantSecret: ?variant_secret_obscured?
>> } ,
>> android: {
>> senderID: "variantid_obscured" ,
>> variantID: "variant_id_obscured" ,
>> variantSecret: "variant_secret_obscured"
>> } ,
>> sendMetricInfo: true,
>> alias: alias1
>> };
>>
>> function HandleAeroGearNotification(event) {
>> console.log(?HandleAeroGearNotification: event => ? +
>> JSON.stringify(event));
>>
>> // Stuff cut for clarity
>> }
>>
>> // Slightly simplified registration event.
>> push.register(HandleAeroGearNotification , function () {
>> console.log(?Success?):
>> } , function () {
>> console.log(?Failure?);
>> } , aeroGearPushConfig);
>>
>> We cannot see any reference to this issue in the JIRA database and
>> wondered if it is a bug or not.
>>
>> If its a bug we are happy to raise it accordingly.
>>
>> Please let us know,
>>
>> Thanks
>> Rob
>>
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>> --
>> Cheers,
>> Erik Jan
>>
>> 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
>> ------------------------------
>>
>> 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
>>
>> --
>> Cheers,
>> Erik Jan
>> ------------------------------
>>
>> 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
>>
>> ------------------------------
>>
>> 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
>>
>>
>
>
> -- 
> Cheers,
>     Erik Jan
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users


From edewit at redhat.com  Wed Jan 13 07:53:38 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Wed, 13 Jan 2016 13:53:38 +0100
Subject: [Aerogear-users] Possible bug in Aerogear Push Cordova/iOS
 implementation but not in the Cordova/Android version
In-Reply-To: <3D0FE23F-93F4-4F90-9834-1539B51D9B25@robertwillett.com>
References: <CED32543-0A98-4EBF-9945-2EBEF7184271@robertwillett.com>
	<CAO2B-fZCqFV+gtSFHaMWs7oErxSwWwmRN9kKHVW8BLWNW0JiMQ@mail.gmail.com>
	<DF12AFF8-A203-4793-85B6-E5D5A411630F@robertwillett.com>
	<CAD_dpu3og=UaA-OOwKBibT=ea4GC1sWMpoYXhWbXieKpXMUG7Q@mail.gmail.com>
	<783F9E55-54CC-4C9E-857F-64A03DB1BC96@robertwillett.com>
	<CAO2B-fbLaN9hhMPtErXkf0mwb5=K2z23DoP69sOu5p0RWW2VQw@mail.gmail.com>
	<23B53EED-5498-4209-A3D3-D6EB9F221B2A@robertwillett.com>
	<E9382606-BFC9-4788-BC60-B9527010D405@robertwillett.com>
	<572042FF-7B4C-4CD0-BC4D-A7057A39A191@robertwillett.com>
	<CAO2B-fYPFoaz+AmyBfO89+tCpiyT5b6SgyN0eGkQmkAXkNkdsw@mail.gmail.com>
	<3D0FE23F-93F4-4F90-9834-1539B51D9B25@robertwillett.com>
Message-ID: <CAO2B-fbqs+cjUKOBLUzvnPMwtxsY7=vvNjJvODfc6yGPGxjnfw@mail.gmail.com>

So you are using a different plugin for push atm? Can you tell me which
one, then we can see if there are differences between how it initialises
and we might be able to fix this.

On Wed, Jan 13, 2016 at 12:07 PM, Rob Willett <
rob.aerogear at robertwillett.com> wrote:

> Erik,
>
> No there are no warnings or any any errors. Errors and warnings we can
> work with, this simply didn?t fire.
>
> At the moment we have got around the issue with a different plugin. We
> didn?t change the architecture at all and the different plugin works.
>
> At the time we thought it was a timing or race condition and we still
> think that.
>
> We have this on the backburner as we need to get a release out. We?ll
> try and revisit it later but it won?t be for a few weeks as Twitter
> interfaces, GPS maps and route matching is on the critical path :)
>
> Thanks
>
> Rob
>
> On 13 Jan 2016, at 9:43, Erik Jan de Wit wrote:
>
> > Seems to be an cordova issue, when loading a lot of javascript makes
> > the
> > plugin skip init, are there warnings in the log about this?
> >
> > On Sun, Dec 20, 2015 at 8:52 PM, Rob Willett
> > <rob.aerogear at robertwillett.com
> >> wrote:
> >
> >> Dear all,
> >>
> >> We *think* we can now reproduce the problem. Clearly writing the last
> >> e-mail has focussed our attention :)
> >>
> >> Summary.
> >>
> >> We have a simple Ionic app that would call the Aerogear notification
> >> handler when notifications were receive in the foreground and when
> >> the app
> >> was in the background. The Aerogear notification handler would
> >> sometimes be
> >> called and sometimes NOT be called when a notification was received
> >> when
> >> the app was not started. See our long previous e-mails detailing the
> >> problem.
> >>
> >> We think we can now reproduce the problem as follows:
> >>
> >> 1.
> >>
> >> Kill the app.
> >> 2.
> >>
> >> Send a notification down to the app.
> >> 3.
> >>
> >> It appears in the iOS notification drawer
> >> 4.
> >>
> >> Click on the notification. if the Aerogear handler has worked then go
> >> to 1 and repeat. We want a failure :)
> >> 5.
> >>
> >> If the Aerogear handler is NOT called, then put the app into the
> >> background using the Home button and then click on the app icon to
> >> resume.
> >> 6.
> >>
> >> The notification is now processed by the Aerogear handler. We can now
> >> see it.
> >>
> >> We are at a loss to explain this, we found it by accident, but we
> >> think it
> >> shows some sort of timing issue somewhere because if we pull out the
> >> various Javascript files the Aerogear plugin seems to work
> >> consistently at
> >> startup. We have checked and checked the JavaScript files and cannot
> >> see
> >> any error with them at all at load time.
> >>
> >> All suggestions welcome now.
> >>
> >> Rob
> >>
> >> On 20 Dec 2015, at 19:26, Rob Willett wrote:
> >>
> >> Erik, Sebastien,
> >>
> >> We?ve spent a significant part of the weekend looking into this
> >> issue and
> >> we have still not got to the bottom of it.
> >>
> >> We have built a very simple Ionic test app that works in isolation.
> >> We
> >> have used the default Ionic tabs at
> >>
> >> http://ionicframework.com/getting-started/
> >>
> >> We then add in our Javascript files as <script> entries in the
> >> index.html
> >> file (shown for example)
> >>
> >> <script src="js/polygon.js"></script>
> >> <script src="js/urls.js"></script>
> >> <script src="js/utilities.js"></script>
> >>
> >> <script src="js/moment.js"></script>
> >> <script src="js/perimeter.js"></script>
> >> <script src="js/leaflet.markercluster-src.js"></script>
> >> <script src="js/cycle.js"></script>
> >> <script src="js/clipper.js"></script>
> >> <script src="js/easy_button.js"></script>
> >> <script src="js/graham_scan.js"></script>
> >> <script src="js/sha.js"></script>
> >> <script src="js/r-tree.js"></script>
> >> <script src="js/angular-leaflet-directive.min.js"></script>
> >> <script src="pouchdb/L.TileLayer.PouchDBCached.js"></script>
> >> <script src="pouchdb/pouchdb-5.1.0.min.js"></script>
> >>
> >> We do NOT call any functions within any of these files, indeed we
> >> make no
> >> reference to these files beyond including them in the index.html
> >> file. Our
> >> dummy html templates make no reference to them. We simply load the
> >> javascript files in. We get no errors from including the files. We
> >> have
> >> used the controllers and services as provided by the dummy sample
> >> Ionic app.
> >>
> >> If we then send foreground notifications, the notifications are
> >> always
> >> handled by the Aerogear notification handler.
> >>
> >> If we send notifications to the app when it is in the background, the
> >> notifications are always handled by the Aerogear notification
> >> handler.
> >>
> >> If we kill by swiping up the app, we get the notifications but when
> >> we
> >> click on the notification from the main IOS screen it is arbitrary as
> >> to
> >> whether the notification is handled by the Aerogear handler when the
> >> app
> >> starts up. Sometimes the handler is called, but once the handler is
> >> not
> >> called, the Aerogear notification handler never appears to be called
> >> again.
> >> If we reinstall the app it sometimes works again and sometimes it
> >> fails.
> >>
> >> We can reinstall the app and the Aerogear notification handler might
> >> be
> >> called or it might not. We just ran the app with 20 tests to the app,
> >> each
> >> time killing the app and then sending down a a notification and it
> >> started
> >> the Aerogear notification handler each time. We then reinstall the
> >> app
> >> again, no changes in the code and it simply doesn?t process any
> >> notification when the app is closed. The notification turns up, but
> >> no
> >> event is called to the Aerogear event handler.
> >>
> >> Given that we are getting arbitrary results from the same codebase,
> >> clearly something is remiss. Sometimes it works and sometimes it
> >> doesn?t.
> >> There is no logic that we can see. We?ve closed down Xcode after
> >> installing, we?ve started and stopped our sample app a few times to
> >> try and
> >> make sure its closed down, ew are sending exactly the same payload
> >> each
> >> time.
> >>
> >> We feel that there is some sort of timing or race condition, or if
> >> this
> >> was a piece of C code, that we are overwriting somewhere we
> >> shouldn?t be.
> >> It has that sort of feeling of a pointer going bad but we cannot see
> >> where
> >> the issue is at all. The fact that we get different results from
> >> doing the
> >> same install is very worrying but we can?t say whether its the
> >> Aerogear
> >> plugin, Ionic or our code.
> >>
> >> Thanks,
> >>
> >> Rob
> >>
> >> On 18 Dec 2015, at 17:26, Rob Willett wrote:
> >>
> >> Erok,
> >>
> >> We?ve not forgotten the notification issue, we?re still working
> >> on it to
> >> try and get to the bottom of it. The problem for us is that its not
> >> so
> >> simple to cut code out and try and reduce the problem down. Our code
> >> is
> >> quite interlinked, for good or for worse.
> >>
> >> We?ve added some simple sound debugging to the Objective C source
> >> for the
> >> Aerogear plugin. This means that we can hear where things are when
> >> the
> >> plugin starts up from a cold start after receiving a notification.
> >> This
> >> works quite well.
> >>
> >> We initially added a beep to here
> >>
> >> - (void)notificationReceived {
> >> NSLog(@"Notification received");
> >>
> >> AudioServicesPlaySystemSound(1005);
> >>
> >>
> >> if (notificationMessage && self.callbackId) {
> >>
> >> and this works whenever we get a notification in the foreground and
> >> when
> >> the app is in the background. We then started tracing backwards in
> >> the
> >> source code to see what called notificationReceived
> >>
> >> We can see it here
> >>
> >> - (void)register:(CDVInvokedUrlCommand *)command; {
> >> NSLog(@"register");
> >> self.callbackId = command.callbackId;
> >>
> >> AudioServicesPlaySystemSound(1007);
> >>
> >> isInline = NO;
> >>
> >> [self.commandDelegate runInBackground:^{
> >> NSMutableDictionary *options = [self parseOptions:command];
> >> [self saveConfig:options];
> >>
> >> // when running under iOS 8 we will use the new API for APNS
> >> registration
> >> #if __IPHONE_OS_VERSION_MAX_ALLOWED >= 80000
> >>   if ([[UIApplication sharedApplication]
> >> respondsToSelector:@selector(registerUserNotificationSettings:)]) {
> >>       UIUserNotificationSettings* notificationSettings =
> >> [UIUserNotificationSettings
> >> settingsForTypes:UIUserNotificationTypeAlert |
> >> UIUserNotificationTypeBadge | UIUserNotificationTypeSound
> >> categories:nil];
> >>       [[UIApplication sharedApplication]
> >> registerUserNotificationSettings:notificationSettings];
> >>       [[UIApplication sharedApplication]
> >> registerForRemoteNotifications];
> >>   } else {
> >>       [[UIApplication sharedApplication]
> >> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge |
> >> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
> >>   }
> >>
> >> #else
> >>   [[UIApplication sharedApplication]
> >> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge |
> >> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
> >> #endif
> >>
> >> CDVPluginResult* pluginResult = [CDVPluginResult
> >> resultWithStatus:CDVCommandStatus_NO_RESULT];
> >> [pluginResult setKeepCallback:@YES];
> >> [self.commandDelegate sendPluginResult:pluginResult
> >> callbackId:command.callbackId];
> >> }];
> >>
> >> if (notificationMessage)            // if there is a pending startup
> >> notification
> >> {
> >> AudioServicesPlaySystemSound(1024);
> >>
> >> [self notificationReceived];    // go ahead and process it
> >> }
> >> }
> >>
> >> So we add some more beeps in to track down whats going on. We add
> >> AudioServicesPlaySystemSound(1007) at the beginning of the function
> >> and add
> >> AudioServicesPlaySystemSound(1024) just before we call the
> >> notificationReceived method.
> >>
> >> We get the first sounds on startup but do NOT get the second set of
> >> sounds. It looks like notificationMessage is not being set at
> >> application
> >> startup.
> >>
> >> Our problem now is that we are not Objective-C developers so we are
> >> struggling to debug much further. So trying to understand how
> >> notificationMessage is set and defined as its declared as @synthesis
> >> is
> >> unclear. We?ll start reading and learning quickly but as this is
> >> new for
> >> us, so we will be slow.
> >>
> >> Any suggestions welcomed,
> >>
> >> Rob
> >>
> >> On 16 Dec 2015, at 16:54, Erik Jan de Wit wrote:
> >>
> >> Hi Rob,
> >>
> >> What you could try is to debug this in xcode, when the notification
> >> is
> >> touched it should launch the app and that will in turn call the JS
> >> callback. Would be good to see if this code is called 100% of the
> >> time.
> >>
> >> You can put a breakpoint here:
> >>
> >>
> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AppDelegate%2Bnotification.m#L56
> >>
> >> That code will execute on cold start and here:
> >>
> >>
> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AGPushPlugin.m#L102
> >>
> >> That is where the onNotification callback gets invoked.
> >>
> >> Hope this helps,
> >>
> >> On Wed, Dec 16, 2015 at 5:14 PM, Rob Willett <
> >> rob.aerogear at robertwillett.com
> >>
> >> wrote:
> >>
> >> Sebastien
> >>
> >> Yes, we do it at that point, $ionicPlatform.ready. I include the
> >> whole of
> >> that area of code for reference but we?re not expecting you to
> >> debug it for
> >> us. Merely to demonstrate its there.
> >>
> >> At the moment all we want the code to do is put an alert up.
> >>
> >> .run(function($ionicPlatform , CordovaService) {
> >> $ionicPlatform.ready(function() {
> >> if (window.StatusBar) {
> >> // org.apache.cordova.statusbar required
> >> StatusBar.styleDefault();
> >> }
> >>
> >> ConsoleLog('<<< Cordova ready >>>');
> >>
> >> /* This seems to remove an annoying page flicker on iOS when the
> >> keyboard
> >> is displayed */
> >> cordova.plugins.Keyboard.disableScroll(true);
> >>
> >> isDeviceReady = true;
> >>
> >> var uuid = "D26FBAF1-2EF2-4614-875F-4497EC4212D5/JFL1-0/ios_app";
> >>
> >> var aeroGearPushConfig = {
> >> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
> >> ios: {
> >> variantID: ?XXXXX?,
> >> variantSecret: ?YYYYYYY?
> >> } ,
> >> // sendMetricInfo: true,
> >> alias: uuid
> >> };
> >>
> >> push.register(function (event) {
> >> alert("EVENT = " + JSON.stringify(event));
> >>
> >> } , function () {
> >> if (1)
> >> {
> >> // alert("AeroGearSuccessHandler: OK " + JSON.stringify(uuid));
> >> // ConsoleLog("UUID = " + uuid);
> >> }
> >> } , function () {
> >> } , aeroGearPushConfig);
> >>
> >> We were still loading up another 18,000 lines of code so we need to
> >> start
> >> pruning that back until we have something that works.
> >>
> >> Rob
> >>
> >> On 16 Dec 2015, at 16:04, Sebastien Blanc wrote:
> >>
> >> In the ionic app when do you do the registration of UPS ? on the
> >> platformReady event ?
> >>
> >> On Wed, Dec 16, 2015 at 4:54 PM, Rob Willett <
> >> rob.aerogear at robertwillett.com
> >>
> >> wrote:
> >>
> >> Erik,
> >>
> >> We have built the simplest possible app we can that uses the Aerogear
> >> push plugin but using the ionic tabs starter kit.
> >>
> >> http://ionicframework.com/getting-started/
> >>
> >> We have taken the code directly from the Cordova simple app that we
> >> have
> >> got working and put it into the Ionic app.
> >>
> >> if we follow your tests as below:
> >>
> >> 1.
> >>
> >> IOS App in foreground, we send a simple push notification from the
> >> Aerogear console - Works OK, We can see the event. Good
> >> 2.
> >>
> >> IOS App in background, we send a simple push notification from the
> >> Aerogear console - Works OK, We can see the event. Good
> >> 3.
> >>
> >> IOS App killed, we send a simple push notification from the Aerogear
> >>
> >> console and some of the time when we click on the notification in the
> >> notification drawer we do NOT get the notification handler called.
> >> Not
> >> so good
> >>
> >> However it does appear to work most of the time with our minimal
> >> Ionic
> >> app, but some of the time it fails. We had a run of 1 in 2 failures
> >> when
> >> we click on the notification. Now we have just done 20 runs in a row,
> >> each time killing the app after receiving the notification and not a
> >> single failure. Nothing changed.
> >>
> >> We cannot find any obvious reason for this so we are still
> >> investigating.
> >>
> >> We have reconfigured our main app to work the same way as the minimal
> >> app but we are still getting the same issues as before, we can see
> >> the
> >> notification in the drawer but clicking on it does NOT call the same
> >> handler with the same code as the minimal app. We get zero calls to
> >> the
> >> notification event handler.
> >>
> >> We are wondering if there is a timing issue somewhere in our code,
> >> but
> >> we can?t see it. We also wondered if the size of the code we are
> >> loading is the cause of a timing issue as well.
> >>
> >> Is there any way of adding more debugging into the Aerogear push
> >> plugin
> >> to see if we can track things down that way?
> >>
> >> Its very frustrating, but thanks for your help to date. It does look
> >> like its an interaction with our code, Ionic and the Aerogear plugin.
> >> My
> >> money is on our code though. We?ll now start pulling working code
> >> out
> >> of our app until we get back to the minimal app. Only 18,604 lines to
> >> go
> >> :)
> >>
> >> Rob
> >>
> >> On 15 Dec 2015, at 10:36, Erik Jan de Wit wrote:
> >>
> >> Hi Rob,
> >>
> >> That would be a bug, although I can not reproduce it, to test it this
> >> is
> >> what I've done to test it:
> >> $ > cordova create push-test <my bundle id>
> >> $ > cordova platform add ios
> >> $ > cordova plugin add aerogear-cordova-push
> >>
> >> copy paste your js code into www/js/index.js onDeviceReady, changed
> >> pushServerUrl and variant info and changed quotes to " (this is your
> >> email
> >> client no doubt) and changed : into ; after console.log("Success")
> >>
> >> Attach Safari debugger and send a message when the app is in the
> >> foreground
> >> and get in the console:
> >>
> >> HandleAeroGearNotification: event =>
> >>
> >>
> >>
> {"alert":"test","foreground":true,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
> >>
> >> I press the home button and send the app to the background send
> >> another
> >> message and 'touch' the message to launch the app:
> >>
> >> HandleAeroGearNotification: event =>
> >>
> >>
> >>
> {"alert":"background","foreground":false,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
> >>
> >> The I kill the app by pressing home twice and swiping over the app to
> >> remove it send another message and 'touch' it to launch the app. This
> >> kills
> >> my safari debugger so no way to see the console log, but in this case
> >> coldstart should be true. To test this better changed the code to
> >> alert
> >> instead of console:
> >>
> >> function HandleAeroGearNotification(event) {
> >> alert("HandleAeroGearNotification: event => " + event.coldstart);
> >>
> >> // Stuff cut for clarity
> >> }
> >>
> >> I send another notification 'touch' it to launch the app and see the
> >> alert
> >> box display the text:
> >>
> >> HandleAeroGearNotification: event => true
> >>
> >> Hope this helps
> >>
> >> On Mon, Dec 14, 2015 at 10:20 PM, Rob Willett <
> >> rob.aerogear at robertwillett.com> wrote:
> >>
> >> Hi,
> >>
> >> We think we have found a possible bug in the Aerogear Cordova 2.0.4
> >> push
> >> plugin specifically on the iOS side.
> >> Summary
> >>
> >> We have two versions of our app, an Android and an IOS version. Both
> >> use
> >> the latest Cordova push plugin 2.0.4. They also both have the latest
> >> Cordova platforms, android 4.1.1, ios 3.9.2. Both the iOS and Android
> >> versions are compiled at the same time. We are running cordova 5.3.3
> >> with
> >> Ionic 1.7.8 (?).
> >>
> >> 1.
> >>
> >> We make sure that both apps are NOT started up on each device. We
> >> also
> >> check they are NOT in the background.
> >> 2.
> >>
> >> We send the same simple notification to each device. This
> >> notification
> >> config is as below, we have anonymised the variants and alias in this
> >> JSON
> >> structure, though we can report that the UPS server sends the data
> >> correctly. We use the additionalData flag to provide the information
> >> necessary to decide which notification has been clicked in the
> >> notification
> >> drawer.
> >>
> >> 'variants' => [?variant1?,?variant2? ],
> >> 'message' => {
> >> 'additionalData' => { 'Disruption_Id' => '107546',
> >> 'EpochTime' => '1450125268'
> >> },
> >> 'alert' => 'Cannon Street (EC4N) (All Directions) at the junction of
> >> King William Street - To facilitate a heavy lift in Cannon Street,
> >> Cannon Street will be closed. Traffic is slow moving on diversion.'
> >> },
> >> 'alias' => [ ?alias1? ],
> >> 'ttl' => 600
> >> };
> >>
> >> 1.
> >>
> >> Both devices show the message, the Android device stacks the message
> >> and the iOS device display an individual message. This looks correct.
> >> 2.
> >>
> >> Clicking on the Android stacked message starts up the app and the
> >> Javascript notification handler we have defined,
> >> HandleAeroGearNotification
> >> is called
> >>
> >> HandleAeroGearNotification: event => {"alert":"Cannon Street (EC4N)
> >> (All Directions) at the junction of King William Street - To
> >> facilitate a heavy lift in Cannon Street, Cannon Street will be
> >> closed. Traffic is slow moving on
> >>
> >>
> diversion.","coldstart":true,"foreground":true,"payload":{"alert":"Cannon
> >>
> >> Street (EC4N) (All Directions) at the junction of King William Street
> >> - To facilitate a heavy lift in Cannon Street, Cannon Street will be
> >> closed. Traffic is slow moving on diversion.","badge":"-1"}}
> >>
> >> 1.
> >>
> >> Clicking on the notification in the notification drawer on the iOS
> >> device also starts our app up correctly but the notification handler,
> >> HandleAeroGearNotification(), is NOT called. The app starts up as
> >> normal as
> >> if the notification had not been clicked. We would expect the
> >> notification
> >> handler to be called in iOS as it is in Android.
> >> 2.
> >>
> >> All notifications are cleared on both Android and iOS correctly when
> >> the app is started up.
> >> 3.
> >>
> >> We define HandleAeroGearNotification as
> >>
> >> var aeroGearPushConfig = {
> >> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
> >> ios: {
> >> variantID: ?variantid_obscured?,
> >> variantSecret: ?variant_secret_obscured?
> >> } ,
> >> android: {
> >> senderID: "variantid_obscured" ,
> >> variantID: "variant_id_obscured" ,
> >> variantSecret: "variant_secret_obscured"
> >> } ,
> >> sendMetricInfo: true,
> >> alias: alias1
> >> };
> >>
> >> function HandleAeroGearNotification(event) {
> >> console.log(?HandleAeroGearNotification: event => ? +
> >> JSON.stringify(event));
> >>
> >> // Stuff cut for clarity
> >> }
> >>
> >> // Slightly simplified registration event.
> >> push.register(HandleAeroGearNotification , function () {
> >> console.log(?Success?):
> >> } , function () {
> >> console.log(?Failure?);
> >> } , aeroGearPushConfig);
> >>
> >> We cannot see any reference to this issue in the JIRA database and
> >> wondered if it is a bug or not.
> >>
> >> If its a bug we are happy to raise it accordingly.
> >>
> >> Please let us know,
> >>
> >> Thanks
> >> Rob
> >>
> >> Aerogear-users mailing list
> >> Aerogear-users at lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/aerogear-users
> >>
> >> --
> >> Cheers,
> >> Erik Jan
> >>
> >> 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
> >> ------------------------------
> >>
> >> 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
> >>
> >> --
> >> Cheers,
> >> Erik Jan
> >> ------------------------------
> >>
> >> 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
> >>
> >> ------------------------------
> >>
> >> 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
> >>
> >>
> >
> >
> > --
> > Cheers,
> >     Erik Jan
> > _______________________________________________
> > 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
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160113/45a30b96/attachment-0001.html 

From rob.aerogear at robertwillett.com  Wed Jan 13 07:56:54 2016
From: rob.aerogear at robertwillett.com (Rob Willett)
Date: Wed, 13 Jan 2016 12:56:54 +0000
Subject: [Aerogear-users] Possible bug in Aerogear Push Cordova/iOS
 implementation but not in the Cordova/Android version
In-Reply-To: <CAO2B-fbqs+cjUKOBLUzvnPMwtxsY7=vvNjJvODfc6yGPGxjnfw@mail.gmail.com>
References: <CED32543-0A98-4EBF-9945-2EBEF7184271@robertwillett.com>
	<CAO2B-fZCqFV+gtSFHaMWs7oErxSwWwmRN9kKHVW8BLWNW0JiMQ@mail.gmail.com>
	<DF12AFF8-A203-4793-85B6-E5D5A411630F@robertwillett.com>
	<CAD_dpu3og=UaA-OOwKBibT=ea4GC1sWMpoYXhWbXieKpXMUG7Q@mail.gmail.com>
	<783F9E55-54CC-4C9E-857F-64A03DB1BC96@robertwillett.com>
	<CAO2B-fbLaN9hhMPtErXkf0mwb5=K2z23DoP69sOu5p0RWW2VQw@mail.gmail.com>
	<23B53EED-5498-4209-A3D3-D6EB9F221B2A@robertwillett.com>
	<E9382606-BFC9-4788-BC60-B9527010D405@robertwillett.com>
	<572042FF-7B4C-4CD0-BC4D-A7057A39A191@robertwillett.com>
	<CAO2B-fYPFoaz+AmyBfO89+tCpiyT5b6SgyN0eGkQmkAXkNkdsw@mail.gmail.com>
	<3D0FE23F-93F4-4F90-9834-1539B51D9B25@robertwillett.com>
	<CAO2B-fbqs+cjUKOBLUzvnPMwtxsY7=vvNjJvODfc6yGPGxjnfw@mail.gmail.com>
Message-ID: <E72F0ECE-DCBC-4BFD-AEE2-BABDA1CB7B4C@robertwillett.com>

Erik,

We moved to PushWoosh as we could not resolve the issues.

Rob

On 13 Jan 2016, at 12:53, Erik Jan de Wit wrote:

> So you are using a different plugin for push atm? Can you tell me 
> which
> one, then we can see if there are differences between how it 
> initialises
> and we might be able to fix this.
>
> On Wed, Jan 13, 2016 at 12:07 PM, Rob Willett <
> rob.aerogear at robertwillett.com> wrote:
>
>> Erik,
>>
>> No there are no warnings or any any errors. Errors and warnings we 
>> can
>> work with, this simply didn?t fire.
>>
>> At the moment we have got around the issue with a different plugin. 
>> We
>> didn?t change the architecture at all and the different plugin 
>> works.
>>
>> At the time we thought it was a timing or race condition and we still
>> think that.
>>
>> We have this on the backburner as we need to get a release out. 
>> We?ll
>> try and revisit it later but it won?t be for a few weeks as Twitter
>> interfaces, GPS maps and route matching is on the critical path :)
>>
>> Thanks
>>
>> Rob
>>
>> On 13 Jan 2016, at 9:43, Erik Jan de Wit wrote:
>>
>>> Seems to be an cordova issue, when loading a lot of javascript makes
>>> the
>>> plugin skip init, are there warnings in the log about this?
>>>
>>> On Sun, Dec 20, 2015 at 8:52 PM, Rob Willett
>>> <rob.aerogear at robertwillett.com
>>>> wrote:
>>>
>>>> Dear all,
>>>>
>>>> We *think* we can now reproduce the problem. Clearly writing the 
>>>> last
>>>> e-mail has focussed our attention :)
>>>>
>>>> Summary.
>>>>
>>>> We have a simple Ionic app that would call the Aerogear 
>>>> notification
>>>> handler when notifications were receive in the foreground and when
>>>> the app
>>>> was in the background. The Aerogear notification handler would
>>>> sometimes be
>>>> called and sometimes NOT be called when a notification was received
>>>> when
>>>> the app was not started. See our long previous e-mails detailing 
>>>> the
>>>> problem.
>>>>
>>>> We think we can now reproduce the problem as follows:
>>>>
>>>> 1.
>>>>
>>>> Kill the app.
>>>> 2.
>>>>
>>>> Send a notification down to the app.
>>>> 3.
>>>>
>>>> It appears in the iOS notification drawer
>>>> 4.
>>>>
>>>> Click on the notification. if the Aerogear handler has worked then 
>>>> go
>>>> to 1 and repeat. We want a failure :)
>>>> 5.
>>>>
>>>> If the Aerogear handler is NOT called, then put the app into the
>>>> background using the Home button and then click on the app icon to
>>>> resume.
>>>> 6.
>>>>
>>>> The notification is now processed by the Aerogear handler. We can 
>>>> now
>>>> see it.
>>>>
>>>> We are at a loss to explain this, we found it by accident, but we
>>>> think it
>>>> shows some sort of timing issue somewhere because if we pull out 
>>>> the
>>>> various Javascript files the Aerogear plugin seems to work
>>>> consistently at
>>>> startup. We have checked and checked the JavaScript files and 
>>>> cannot
>>>> see
>>>> any error with them at all at load time.
>>>>
>>>> All suggestions welcome now.
>>>>
>>>> Rob
>>>>
>>>> On 20 Dec 2015, at 19:26, Rob Willett wrote:
>>>>
>>>> Erik, Sebastien,
>>>>
>>>> We?ve spent a significant part of the weekend looking into this
>>>> issue and
>>>> we have still not got to the bottom of it.
>>>>
>>>> We have built a very simple Ionic test app that works in isolation.
>>>> We
>>>> have used the default Ionic tabs at
>>>>
>>>> http://ionicframework.com/getting-started/
>>>>
>>>> We then add in our Javascript files as <script> entries in the
>>>> index.html
>>>> file (shown for example)
>>>>
>>>> <script src="js/polygon.js"></script>
>>>> <script src="js/urls.js"></script>
>>>> <script src="js/utilities.js"></script>
>>>>
>>>> <script src="js/moment.js"></script>
>>>> <script src="js/perimeter.js"></script>
>>>> <script src="js/leaflet.markercluster-src.js"></script>
>>>> <script src="js/cycle.js"></script>
>>>> <script src="js/clipper.js"></script>
>>>> <script src="js/easy_button.js"></script>
>>>> <script src="js/graham_scan.js"></script>
>>>> <script src="js/sha.js"></script>
>>>> <script src="js/r-tree.js"></script>
>>>> <script src="js/angular-leaflet-directive.min.js"></script>
>>>> <script src="pouchdb/L.TileLayer.PouchDBCached.js"></script>
>>>> <script src="pouchdb/pouchdb-5.1.0.min.js"></script>
>>>>
>>>> We do NOT call any functions within any of these files, indeed we
>>>> make no
>>>> reference to these files beyond including them in the index.html
>>>> file. Our
>>>> dummy html templates make no reference to them. We simply load the
>>>> javascript files in. We get no errors from including the files. We
>>>> have
>>>> used the controllers and services as provided by the dummy sample
>>>> Ionic app.
>>>>
>>>> If we then send foreground notifications, the notifications are
>>>> always
>>>> handled by the Aerogear notification handler.
>>>>
>>>> If we send notifications to the app when it is in the background, 
>>>> the
>>>> notifications are always handled by the Aerogear notification
>>>> handler.
>>>>
>>>> If we kill by swiping up the app, we get the notifications but when
>>>> we
>>>> click on the notification from the main IOS screen it is arbitrary 
>>>> as
>>>> to
>>>> whether the notification is handled by the Aerogear handler when 
>>>> the
>>>> app
>>>> starts up. Sometimes the handler is called, but once the handler is
>>>> not
>>>> called, the Aerogear notification handler never appears to be 
>>>> called
>>>> again.
>>>> If we reinstall the app it sometimes works again and sometimes it
>>>> fails.
>>>>
>>>> We can reinstall the app and the Aerogear notification handler 
>>>> might
>>>> be
>>>> called or it might not. We just ran the app with 20 tests to the 
>>>> app,
>>>> each
>>>> time killing the app and then sending down a a notification and it
>>>> started
>>>> the Aerogear notification handler each time. We then reinstall the
>>>> app
>>>> again, no changes in the code and it simply doesn?t process any
>>>> notification when the app is closed. The notification turns up, but
>>>> no
>>>> event is called to the Aerogear event handler.
>>>>
>>>> Given that we are getting arbitrary results from the same codebase,
>>>> clearly something is remiss. Sometimes it works and sometimes it
>>>> doesn?t.
>>>> There is no logic that we can see. We?ve closed down Xcode after
>>>> installing, we?ve started and stopped our sample app a few times 
>>>> to
>>>> try and
>>>> make sure its closed down, ew are sending exactly the same payload
>>>> each
>>>> time.
>>>>
>>>> We feel that there is some sort of timing or race condition, or if
>>>> this
>>>> was a piece of C code, that we are overwriting somewhere we
>>>> shouldn?t be.
>>>> It has that sort of feeling of a pointer going bad but we cannot 
>>>> see
>>>> where
>>>> the issue is at all. The fact that we get different results from
>>>> doing the
>>>> same install is very worrying but we can?t say whether its the
>>>> Aerogear
>>>> plugin, Ionic or our code.
>>>>
>>>> Thanks,
>>>>
>>>> Rob
>>>>
>>>> On 18 Dec 2015, at 17:26, Rob Willett wrote:
>>>>
>>>> Erok,
>>>>
>>>> We?ve not forgotten the notification issue, we?re still working
>>>> on it to
>>>> try and get to the bottom of it. The problem for us is that its not
>>>> so
>>>> simple to cut code out and try and reduce the problem down. Our 
>>>> code
>>>> is
>>>> quite interlinked, for good or for worse.
>>>>
>>>> We?ve added some simple sound debugging to the Objective C source
>>>> for the
>>>> Aerogear plugin. This means that we can hear where things are when
>>>> the
>>>> plugin starts up from a cold start after receiving a notification.
>>>> This
>>>> works quite well.
>>>>
>>>> We initially added a beep to here
>>>>
>>>> - (void)notificationReceived {
>>>> NSLog(@"Notification received");
>>>>
>>>> AudioServicesPlaySystemSound(1005);
>>>>
>>>>
>>>> if (notificationMessage && self.callbackId) {
>>>>
>>>> and this works whenever we get a notification in the foreground and
>>>> when
>>>> the app is in the background. We then started tracing backwards in
>>>> the
>>>> source code to see what called notificationReceived
>>>>
>>>> We can see it here
>>>>
>>>> - (void)register:(CDVInvokedUrlCommand *)command; {
>>>> NSLog(@"register");
>>>> self.callbackId = command.callbackId;
>>>>
>>>> AudioServicesPlaySystemSound(1007);
>>>>
>>>> isInline = NO;
>>>>
>>>> [self.commandDelegate runInBackground:^{
>>>> NSMutableDictionary *options = [self parseOptions:command];
>>>> [self saveConfig:options];
>>>>
>>>> // when running under iOS 8 we will use the new API for APNS
>>>> registration
>>>> #if __IPHONE_OS_VERSION_MAX_ALLOWED >= 80000
>>>> if ([[UIApplication sharedApplication]
>>>> respondsToSelector:@selector(registerUserNotificationSettings:)]) {
>>>>    UIUserNotificationSettings* notificationSettings =
>>>> [UIUserNotificationSettings
>>>> settingsForTypes:UIUserNotificationTypeAlert |
>>>> UIUserNotificationTypeBadge | UIUserNotificationTypeSound
>>>> categories:nil];
>>>>    [[UIApplication sharedApplication]
>>>> registerUserNotificationSettings:notificationSettings];
>>>>    [[UIApplication sharedApplication]
>>>> registerForRemoteNotifications];
>>>> } else {
>>>>    [[UIApplication sharedApplication]
>>>> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge 
>>>> |
>>>> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>>>> }
>>>>
>>>> #else
>>>> [[UIApplication sharedApplication]
>>>> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge 
>>>> |
>>>> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>>>> #endif
>>>>
>>>> CDVPluginResult* pluginResult = [CDVPluginResult
>>>> resultWithStatus:CDVCommandStatus_NO_RESULT];
>>>> [pluginResult setKeepCallback:@YES];
>>>> [self.commandDelegate sendPluginResult:pluginResult
>>>> callbackId:command.callbackId];
>>>> }];
>>>>
>>>> if (notificationMessage)            // if there is a pending 
>>>> startup
>>>> notification
>>>> {
>>>> AudioServicesPlaySystemSound(1024);
>>>>
>>>> [self notificationReceived];    // go ahead and process it
>>>> }
>>>> }
>>>>
>>>> So we add some more beeps in to track down whats going on. We add
>>>> AudioServicesPlaySystemSound(1007) at the beginning of the function
>>>> and add
>>>> AudioServicesPlaySystemSound(1024) just before we call the
>>>> notificationReceived method.
>>>>
>>>> We get the first sounds on startup but do NOT get the second set of
>>>> sounds. It looks like notificationMessage is not being set at
>>>> application
>>>> startup.
>>>>
>>>> Our problem now is that we are not Objective-C developers so we are
>>>> struggling to debug much further. So trying to understand how
>>>> notificationMessage is set and defined as its declared as 
>>>> @synthesis
>>>> is
>>>> unclear. We?ll start reading and learning quickly but as this is
>>>> new for
>>>> us, so we will be slow.
>>>>
>>>> Any suggestions welcomed,
>>>>
>>>> Rob
>>>>
>>>> On 16 Dec 2015, at 16:54, Erik Jan de Wit wrote:
>>>>
>>>> Hi Rob,
>>>>
>>>> What you could try is to debug this in xcode, when the notification
>>>> is
>>>> touched it should launch the app and that will in turn call the JS
>>>> callback. Would be good to see if this code is called 100% of the
>>>> time.
>>>>
>>>> You can put a breakpoint here:
>>>>
>>>>
>> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AppDelegate%2Bnotification.m#L56
>>>>
>>>> That code will execute on cold start and here:
>>>>
>>>>
>> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AGPushPlugin.m#L102
>>>>
>>>> That is where the onNotification callback gets invoked.
>>>>
>>>> Hope this helps,
>>>>
>>>> On Wed, Dec 16, 2015 at 5:14 PM, Rob Willett <
>>>> rob.aerogear at robertwillett.com
>>>>
>>>> wrote:
>>>>
>>>> Sebastien
>>>>
>>>> Yes, we do it at that point, $ionicPlatform.ready. I include the
>>>> whole of
>>>> that area of code for reference but we?re not expecting you to
>>>> debug it for
>>>> us. Merely to demonstrate its there.
>>>>
>>>> At the moment all we want the code to do is put an alert up.
>>>>
>>>> .run(function($ionicPlatform , CordovaService) {
>>>> $ionicPlatform.ready(function() {
>>>> if (window.StatusBar) {
>>>> // org.apache.cordova.statusbar required
>>>> StatusBar.styleDefault();
>>>> }
>>>>
>>>> ConsoleLog('<<< Cordova ready >>>');
>>>>
>>>> /* This seems to remove an annoying page flicker on iOS when the
>>>> keyboard
>>>> is displayed */
>>>> cordova.plugins.Keyboard.disableScroll(true);
>>>>
>>>> isDeviceReady = true;
>>>>
>>>> var uuid = "D26FBAF1-2EF2-4614-875F-4497EC4212D5/JFL1-0/ios_app";
>>>>
>>>> var aeroGearPushConfig = {
>>>> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>>>> ios: {
>>>> variantID: ?XXXXX?,
>>>> variantSecret: ?YYYYYYY?
>>>> } ,
>>>> // sendMetricInfo: true,
>>>> alias: uuid
>>>> };
>>>>
>>>> push.register(function (event) {
>>>> alert("EVENT = " + JSON.stringify(event));
>>>>
>>>> } , function () {
>>>> if (1)
>>>> {
>>>> // alert("AeroGearSuccessHandler: OK " + JSON.stringify(uuid));
>>>> // ConsoleLog("UUID = " + uuid);
>>>> }
>>>> } , function () {
>>>> } , aeroGearPushConfig);
>>>>
>>>> We were still loading up another 18,000 lines of code so we need to
>>>> start
>>>> pruning that back until we have something that works.
>>>>
>>>> Rob
>>>>
>>>> On 16 Dec 2015, at 16:04, Sebastien Blanc wrote:
>>>>
>>>> In the ionic app when do you do the registration of UPS ? on the
>>>> platformReady event ?
>>>>
>>>> On Wed, Dec 16, 2015 at 4:54 PM, Rob Willett <
>>>> rob.aerogear at robertwillett.com
>>>>
>>>> wrote:
>>>>
>>>> Erik,
>>>>
>>>> We have built the simplest possible app we can that uses the 
>>>> Aerogear
>>>> push plugin but using the ionic tabs starter kit.
>>>>
>>>> http://ionicframework.com/getting-started/
>>>>
>>>> We have taken the code directly from the Cordova simple app that we
>>>> have
>>>> got working and put it into the Ionic app.
>>>>
>>>> if we follow your tests as below:
>>>>
>>>> 1.
>>>>
>>>> IOS App in foreground, we send a simple push notification from the
>>>> Aerogear console - Works OK, We can see the event. Good
>>>> 2.
>>>>
>>>> IOS App in background, we send a simple push notification from the
>>>> Aerogear console - Works OK, We can see the event. Good
>>>> 3.
>>>>
>>>> IOS App killed, we send a simple push notification from the 
>>>> Aerogear
>>>>
>>>> console and some of the time when we click on the notification in 
>>>> the
>>>> notification drawer we do NOT get the notification handler called.
>>>> Not
>>>> so good
>>>>
>>>> However it does appear to work most of the time with our minimal
>>>> Ionic
>>>> app, but some of the time it fails. We had a run of 1 in 2 failures
>>>> when
>>>> we click on the notification. Now we have just done 20 runs in a 
>>>> row,
>>>> each time killing the app after receiving the notification and not 
>>>> a
>>>> single failure. Nothing changed.
>>>>
>>>> We cannot find any obvious reason for this so we are still
>>>> investigating.
>>>>
>>>> We have reconfigured our main app to work the same way as the 
>>>> minimal
>>>> app but we are still getting the same issues as before, we can see
>>>> the
>>>> notification in the drawer but clicking on it does NOT call the 
>>>> same
>>>> handler with the same code as the minimal app. We get zero calls to
>>>> the
>>>> notification event handler.
>>>>
>>>> We are wondering if there is a timing issue somewhere in our code,
>>>> but
>>>> we can?t see it. We also wondered if the size of the code we are
>>>> loading is the cause of a timing issue as well.
>>>>
>>>> Is there any way of adding more debugging into the Aerogear push
>>>> plugin
>>>> to see if we can track things down that way?
>>>>
>>>> Its very frustrating, but thanks for your help to date. It does 
>>>> look
>>>> like its an interaction with our code, Ionic and the Aerogear 
>>>> plugin.
>>>> My
>>>> money is on our code though. We?ll now start pulling working code
>>>> out
>>>> of our app until we get back to the minimal app. Only 18,604 lines 
>>>> to
>>>> go
>>>> :)
>>>>
>>>> Rob
>>>>
>>>> On 15 Dec 2015, at 10:36, Erik Jan de Wit wrote:
>>>>
>>>> Hi Rob,
>>>>
>>>> That would be a bug, although I can not reproduce it, to test it 
>>>> this
>>>> is
>>>> what I've done to test it:
>>>> $ > cordova create push-test <my bundle id>
>>>> $ > cordova platform add ios
>>>> $ > cordova plugin add aerogear-cordova-push
>>>>
>>>> copy paste your js code into www/js/index.js onDeviceReady, changed
>>>> pushServerUrl and variant info and changed quotes to " (this is 
>>>> your
>>>> email
>>>> client no doubt) and changed : into ; after console.log("Success")
>>>>
>>>> Attach Safari debugger and send a message when the app is in the
>>>> foreground
>>>> and get in the console:
>>>>
>>>> HandleAeroGearNotification: event =>
>>>>
>>>>
>>>>
>> {"alert":"test","foreground":true,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>>>>
>>>> I press the home button and send the app to the background send
>>>> another
>>>> message and 'touch' the message to launch the app:
>>>>
>>>> HandleAeroGearNotification: event =>
>>>>
>>>>
>>>>
>> {"alert":"background","foreground":false,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>>>>
>>>> The I kill the app by pressing home twice and swiping over the app 
>>>> to
>>>> remove it send another message and 'touch' it to launch the app. 
>>>> This
>>>> kills
>>>> my safari debugger so no way to see the console log, but in this 
>>>> case
>>>> coldstart should be true. To test this better changed the code to
>>>> alert
>>>> instead of console:
>>>>
>>>> function HandleAeroGearNotification(event) {
>>>> alert("HandleAeroGearNotification: event => " + event.coldstart);
>>>>
>>>> // Stuff cut for clarity
>>>> }
>>>>
>>>> I send another notification 'touch' it to launch the app and see 
>>>> the
>>>> alert
>>>> box display the text:
>>>>
>>>> HandleAeroGearNotification: event => true
>>>>
>>>> Hope this helps
>>>>
>>>> On Mon, Dec 14, 2015 at 10:20 PM, Rob Willett <
>>>> rob.aerogear at robertwillett.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> We think we have found a possible bug in the Aerogear Cordova 2.0.4
>>>> push
>>>> plugin specifically on the iOS side.
>>>> Summary
>>>>
>>>> We have two versions of our app, an Android and an IOS version. 
>>>> Both
>>>> use
>>>> the latest Cordova push plugin 2.0.4. They also both have the 
>>>> latest
>>>> Cordova platforms, android 4.1.1, ios 3.9.2. Both the iOS and 
>>>> Android
>>>> versions are compiled at the same time. We are running cordova 
>>>> 5.3.3
>>>> with
>>>> Ionic 1.7.8 (?).
>>>>
>>>> 1.
>>>>
>>>> We make sure that both apps are NOT started up on each device. We
>>>> also
>>>> check they are NOT in the background.
>>>> 2.
>>>>
>>>> We send the same simple notification to each device. This
>>>> notification
>>>> config is as below, we have anonymised the variants and alias in 
>>>> this
>>>> JSON
>>>> structure, though we can report that the UPS server sends the data
>>>> correctly. We use the additionalData flag to provide the 
>>>> information
>>>> necessary to decide which notification has been clicked in the
>>>> notification
>>>> drawer.
>>>>
>>>> 'variants' => [?variant1?,?variant2? ],
>>>> 'message' => {
>>>> 'additionalData' => { 'Disruption_Id' => '107546',
>>>> 'EpochTime' => '1450125268'
>>>> },
>>>> 'alert' => 'Cannon Street (EC4N) (All Directions) at the junction 
>>>> of
>>>> King William Street - To facilitate a heavy lift in Cannon Street,
>>>> Cannon Street will be closed. Traffic is slow moving on diversion.'
>>>> },
>>>> 'alias' => [ ?alias1? ],
>>>> 'ttl' => 600
>>>> };
>>>>
>>>> 1.
>>>>
>>>> Both devices show the message, the Android device stacks the 
>>>> message
>>>> and the iOS device display an individual message. This looks 
>>>> correct.
>>>> 2.
>>>>
>>>> Clicking on the Android stacked message starts up the app and the
>>>> Javascript notification handler we have defined,
>>>> HandleAeroGearNotification
>>>> is called
>>>>
>>>> HandleAeroGearNotification: event => {"alert":"Cannon Street (EC4N)
>>>> (All Directions) at the junction of King William Street - To
>>>> facilitate a heavy lift in Cannon Street, Cannon Street will be
>>>> closed. Traffic is slow moving on
>>>>
>>>>
>> diversion.","coldstart":true,"foreground":true,"payload":{"alert":"Cannon
>>>>
>>>> Street (EC4N) (All Directions) at the junction of King William 
>>>> Street
>>>> - To facilitate a heavy lift in Cannon Street, Cannon Street will 
>>>> be
>>>> closed. Traffic is slow moving on diversion.","badge":"-1"}}
>>>>
>>>> 1.
>>>>
>>>> Clicking on the notification in the notification drawer on the iOS
>>>> device also starts our app up correctly but the notification 
>>>> handler,
>>>> HandleAeroGearNotification(), is NOT called. The app starts up as
>>>> normal as
>>>> if the notification had not been clicked. We would expect the
>>>> notification
>>>> handler to be called in iOS as it is in Android.
>>>> 2.
>>>>
>>>> All notifications are cleared on both Android and iOS correctly 
>>>> when
>>>> the app is started up.
>>>> 3.
>>>>
>>>> We define HandleAeroGearNotification as
>>>>
>>>> var aeroGearPushConfig = {
>>>> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>>>> ios: {
>>>> variantID: ?variantid_obscured?,
>>>> variantSecret: ?variant_secret_obscured?
>>>> } ,
>>>> android: {
>>>> senderID: "variantid_obscured" ,
>>>> variantID: "variant_id_obscured" ,
>>>> variantSecret: "variant_secret_obscured"
>>>> } ,
>>>> sendMetricInfo: true,
>>>> alias: alias1
>>>> };
>>>>
>>>> function HandleAeroGearNotification(event) {
>>>> console.log(?HandleAeroGearNotification: event => ? +
>>>> JSON.stringify(event));
>>>>
>>>> // Stuff cut for clarity
>>>> }
>>>>
>>>> // Slightly simplified registration event.
>>>> push.register(HandleAeroGearNotification , function () {
>>>> console.log(?Success?):
>>>> } , function () {
>>>> console.log(?Failure?);
>>>> } , aeroGearPushConfig);
>>>>
>>>> We cannot see any reference to this issue in the JIRA database and
>>>> wondered if it is a bug or not.
>>>>
>>>> If its a bug we are happy to raise it accordingly.
>>>>
>>>> Please let us know,
>>>>
>>>> Thanks
>>>> Rob
>>>>
>>>> Aerogear-users mailing list
>>>> Aerogear-users at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>>
>>>> --
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>> 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
>>>> ------------------------------
>>>>
>>>> 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
>>>>
>>>> --
>>>> Cheers,
>>>> Erik Jan
>>>> ------------------------------
>>>>
>>>> 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
>>>>
>>>> ------------------------------
>>>>
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Cheers,
>>>  Erik Jan
>>> _______________________________________________
>>> 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
>>
>
>
>
> -- 
> Cheers,
>     Erik Jan
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users


From rob.aerogear at robertwillett.com  Wed Jan 13 07:58:13 2016
From: rob.aerogear at robertwillett.com (Rob Willett)
Date: Wed, 13 Jan 2016 12:58:13 +0000
Subject: [Aerogear-users] Possible bug in Aerogear Push Cordova/iOS
 implementation but not in the Cordova/Android version
In-Reply-To: <CAO2B-fbqs+cjUKOBLUzvnPMwtxsY7=vvNjJvODfc6yGPGxjnfw@mail.gmail.com>
References: <CED32543-0A98-4EBF-9945-2EBEF7184271@robertwillett.com>
	<CAO2B-fZCqFV+gtSFHaMWs7oErxSwWwmRN9kKHVW8BLWNW0JiMQ@mail.gmail.com>
	<DF12AFF8-A203-4793-85B6-E5D5A411630F@robertwillett.com>
	<CAD_dpu3og=UaA-OOwKBibT=ea4GC1sWMpoYXhWbXieKpXMUG7Q@mail.gmail.com>
	<783F9E55-54CC-4C9E-857F-64A03DB1BC96@robertwillett.com>
	<CAO2B-fbLaN9hhMPtErXkf0mwb5=K2z23DoP69sOu5p0RWW2VQw@mail.gmail.com>
	<23B53EED-5498-4209-A3D3-D6EB9F221B2A@robertwillett.com>
	<E9382606-BFC9-4788-BC60-B9527010D405@robertwillett.com>
	<572042FF-7B4C-4CD0-BC4D-A7057A39A191@robertwillett.com>
	<CAO2B-fYPFoaz+AmyBfO89+tCpiyT5b6SgyN0eGkQmkAXkNkdsw@mail.gmail.com>
	<3D0FE23F-93F4-4F90-9834-1539B51D9B25@robertwillett.com>
	<CAO2B-fbqs+cjUKOBLUzvnPMwtxsY7=vvNjJvODfc6yGPGxjnfw@mail.gmail.com>
Message-ID: <1ED7715B-08B7-4187-BB89-B2C6240BC1D7@robertwillett.com>

Erik,

Pressed the return key too early.

We also tried it with OneSignal as well and that was fine.

Rob

On 13 Jan 2016, at 12:53, Erik Jan de Wit wrote:

> So you are using a different plugin for push atm? Can you tell me 
> which
> one, then we can see if there are differences between how it 
> initialises
> and we might be able to fix this.
>
> On Wed, Jan 13, 2016 at 12:07 PM, Rob Willett <
> rob.aerogear at robertwillett.com> wrote:
>
>> Erik,
>>
>> No there are no warnings or any any errors. Errors and warnings we 
>> can
>> work with, this simply didn?t fire.
>>
>> At the moment we have got around the issue with a different plugin. 
>> We
>> didn?t change the architecture at all and the different plugin 
>> works.
>>
>> At the time we thought it was a timing or race condition and we still
>> think that.
>>
>> We have this on the backburner as we need to get a release out. 
>> We?ll
>> try and revisit it later but it won?t be for a few weeks as Twitter
>> interfaces, GPS maps and route matching is on the critical path :)
>>
>> Thanks
>>
>> Rob
>>
>> On 13 Jan 2016, at 9:43, Erik Jan de Wit wrote:
>>
>>> Seems to be an cordova issue, when loading a lot of javascript makes
>>> the
>>> plugin skip init, are there warnings in the log about this?
>>>
>>> On Sun, Dec 20, 2015 at 8:52 PM, Rob Willett
>>> <rob.aerogear at robertwillett.com
>>>> wrote:
>>>
>>>> Dear all,
>>>>
>>>> We *think* we can now reproduce the problem. Clearly writing the 
>>>> last
>>>> e-mail has focussed our attention :)
>>>>
>>>> Summary.
>>>>
>>>> We have a simple Ionic app that would call the Aerogear 
>>>> notification
>>>> handler when notifications were receive in the foreground and when
>>>> the app
>>>> was in the background. The Aerogear notification handler would
>>>> sometimes be
>>>> called and sometimes NOT be called when a notification was received
>>>> when
>>>> the app was not started. See our long previous e-mails detailing 
>>>> the
>>>> problem.
>>>>
>>>> We think we can now reproduce the problem as follows:
>>>>
>>>> 1.
>>>>
>>>> Kill the app.
>>>> 2.
>>>>
>>>> Send a notification down to the app.
>>>> 3.
>>>>
>>>> It appears in the iOS notification drawer
>>>> 4.
>>>>
>>>> Click on the notification. if the Aerogear handler has worked then 
>>>> go
>>>> to 1 and repeat. We want a failure :)
>>>> 5.
>>>>
>>>> If the Aerogear handler is NOT called, then put the app into the
>>>> background using the Home button and then click on the app icon to
>>>> resume.
>>>> 6.
>>>>
>>>> The notification is now processed by the Aerogear handler. We can 
>>>> now
>>>> see it.
>>>>
>>>> We are at a loss to explain this, we found it by accident, but we
>>>> think it
>>>> shows some sort of timing issue somewhere because if we pull out 
>>>> the
>>>> various Javascript files the Aerogear plugin seems to work
>>>> consistently at
>>>> startup. We have checked and checked the JavaScript files and 
>>>> cannot
>>>> see
>>>> any error with them at all at load time.
>>>>
>>>> All suggestions welcome now.
>>>>
>>>> Rob
>>>>
>>>> On 20 Dec 2015, at 19:26, Rob Willett wrote:
>>>>
>>>> Erik, Sebastien,
>>>>
>>>> We?ve spent a significant part of the weekend looking into this
>>>> issue and
>>>> we have still not got to the bottom of it.
>>>>
>>>> We have built a very simple Ionic test app that works in isolation.
>>>> We
>>>> have used the default Ionic tabs at
>>>>
>>>> http://ionicframework.com/getting-started/
>>>>
>>>> We then add in our Javascript files as <script> entries in the
>>>> index.html
>>>> file (shown for example)
>>>>
>>>> <script src="js/polygon.js"></script>
>>>> <script src="js/urls.js"></script>
>>>> <script src="js/utilities.js"></script>
>>>>
>>>> <script src="js/moment.js"></script>
>>>> <script src="js/perimeter.js"></script>
>>>> <script src="js/leaflet.markercluster-src.js"></script>
>>>> <script src="js/cycle.js"></script>
>>>> <script src="js/clipper.js"></script>
>>>> <script src="js/easy_button.js"></script>
>>>> <script src="js/graham_scan.js"></script>
>>>> <script src="js/sha.js"></script>
>>>> <script src="js/r-tree.js"></script>
>>>> <script src="js/angular-leaflet-directive.min.js"></script>
>>>> <script src="pouchdb/L.TileLayer.PouchDBCached.js"></script>
>>>> <script src="pouchdb/pouchdb-5.1.0.min.js"></script>
>>>>
>>>> We do NOT call any functions within any of these files, indeed we
>>>> make no
>>>> reference to these files beyond including them in the index.html
>>>> file. Our
>>>> dummy html templates make no reference to them. We simply load the
>>>> javascript files in. We get no errors from including the files. We
>>>> have
>>>> used the controllers and services as provided by the dummy sample
>>>> Ionic app.
>>>>
>>>> If we then send foreground notifications, the notifications are
>>>> always
>>>> handled by the Aerogear notification handler.
>>>>
>>>> If we send notifications to the app when it is in the background, 
>>>> the
>>>> notifications are always handled by the Aerogear notification
>>>> handler.
>>>>
>>>> If we kill by swiping up the app, we get the notifications but when
>>>> we
>>>> click on the notification from the main IOS screen it is arbitrary 
>>>> as
>>>> to
>>>> whether the notification is handled by the Aerogear handler when 
>>>> the
>>>> app
>>>> starts up. Sometimes the handler is called, but once the handler is
>>>> not
>>>> called, the Aerogear notification handler never appears to be 
>>>> called
>>>> again.
>>>> If we reinstall the app it sometimes works again and sometimes it
>>>> fails.
>>>>
>>>> We can reinstall the app and the Aerogear notification handler 
>>>> might
>>>> be
>>>> called or it might not. We just ran the app with 20 tests to the 
>>>> app,
>>>> each
>>>> time killing the app and then sending down a a notification and it
>>>> started
>>>> the Aerogear notification handler each time. We then reinstall the
>>>> app
>>>> again, no changes in the code and it simply doesn?t process any
>>>> notification when the app is closed. The notification turns up, but
>>>> no
>>>> event is called to the Aerogear event handler.
>>>>
>>>> Given that we are getting arbitrary results from the same codebase,
>>>> clearly something is remiss. Sometimes it works and sometimes it
>>>> doesn?t.
>>>> There is no logic that we can see. We?ve closed down Xcode after
>>>> installing, we?ve started and stopped our sample app a few times 
>>>> to
>>>> try and
>>>> make sure its closed down, ew are sending exactly the same payload
>>>> each
>>>> time.
>>>>
>>>> We feel that there is some sort of timing or race condition, or if
>>>> this
>>>> was a piece of C code, that we are overwriting somewhere we
>>>> shouldn?t be.
>>>> It has that sort of feeling of a pointer going bad but we cannot 
>>>> see
>>>> where
>>>> the issue is at all. The fact that we get different results from
>>>> doing the
>>>> same install is very worrying but we can?t say whether its the
>>>> Aerogear
>>>> plugin, Ionic or our code.
>>>>
>>>> Thanks,
>>>>
>>>> Rob
>>>>
>>>> On 18 Dec 2015, at 17:26, Rob Willett wrote:
>>>>
>>>> Erok,
>>>>
>>>> We?ve not forgotten the notification issue, we?re still working
>>>> on it to
>>>> try and get to the bottom of it. The problem for us is that its not
>>>> so
>>>> simple to cut code out and try and reduce the problem down. Our 
>>>> code
>>>> is
>>>> quite interlinked, for good or for worse.
>>>>
>>>> We?ve added some simple sound debugging to the Objective C source
>>>> for the
>>>> Aerogear plugin. This means that we can hear where things are when
>>>> the
>>>> plugin starts up from a cold start after receiving a notification.
>>>> This
>>>> works quite well.
>>>>
>>>> We initially added a beep to here
>>>>
>>>> - (void)notificationReceived {
>>>> NSLog(@"Notification received");
>>>>
>>>> AudioServicesPlaySystemSound(1005);
>>>>
>>>>
>>>> if (notificationMessage && self.callbackId) {
>>>>
>>>> and this works whenever we get a notification in the foreground and
>>>> when
>>>> the app is in the background. We then started tracing backwards in
>>>> the
>>>> source code to see what called notificationReceived
>>>>
>>>> We can see it here
>>>>
>>>> - (void)register:(CDVInvokedUrlCommand *)command; {
>>>> NSLog(@"register");
>>>> self.callbackId = command.callbackId;
>>>>
>>>> AudioServicesPlaySystemSound(1007);
>>>>
>>>> isInline = NO;
>>>>
>>>> [self.commandDelegate runInBackground:^{
>>>> NSMutableDictionary *options = [self parseOptions:command];
>>>> [self saveConfig:options];
>>>>
>>>> // when running under iOS 8 we will use the new API for APNS
>>>> registration
>>>> #if __IPHONE_OS_VERSION_MAX_ALLOWED >= 80000
>>>> if ([[UIApplication sharedApplication]
>>>> respondsToSelector:@selector(registerUserNotificationSettings:)]) {
>>>>    UIUserNotificationSettings* notificationSettings =
>>>> [UIUserNotificationSettings
>>>> settingsForTypes:UIUserNotificationTypeAlert |
>>>> UIUserNotificationTypeBadge | UIUserNotificationTypeSound
>>>> categories:nil];
>>>>    [[UIApplication sharedApplication]
>>>> registerUserNotificationSettings:notificationSettings];
>>>>    [[UIApplication sharedApplication]
>>>> registerForRemoteNotifications];
>>>> } else {
>>>>    [[UIApplication sharedApplication]
>>>> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge 
>>>> |
>>>> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>>>> }
>>>>
>>>> #else
>>>> [[UIApplication sharedApplication]
>>>> registerForRemoteNotificationTypes: (UIRemoteNotificationTypeBadge 
>>>> |
>>>> UIRemoteNotificationTypeSound | UIRemoteNotificationTypeAlert)];
>>>> #endif
>>>>
>>>> CDVPluginResult* pluginResult = [CDVPluginResult
>>>> resultWithStatus:CDVCommandStatus_NO_RESULT];
>>>> [pluginResult setKeepCallback:@YES];
>>>> [self.commandDelegate sendPluginResult:pluginResult
>>>> callbackId:command.callbackId];
>>>> }];
>>>>
>>>> if (notificationMessage)            // if there is a pending 
>>>> startup
>>>> notification
>>>> {
>>>> AudioServicesPlaySystemSound(1024);
>>>>
>>>> [self notificationReceived];    // go ahead and process it
>>>> }
>>>> }
>>>>
>>>> So we add some more beeps in to track down whats going on. We add
>>>> AudioServicesPlaySystemSound(1007) at the beginning of the function
>>>> and add
>>>> AudioServicesPlaySystemSound(1024) just before we call the
>>>> notificationReceived method.
>>>>
>>>> We get the first sounds on startup but do NOT get the second set of
>>>> sounds. It looks like notificationMessage is not being set at
>>>> application
>>>> startup.
>>>>
>>>> Our problem now is that we are not Objective-C developers so we are
>>>> struggling to debug much further. So trying to understand how
>>>> notificationMessage is set and defined as its declared as 
>>>> @synthesis
>>>> is
>>>> unclear. We?ll start reading and learning quickly but as this is
>>>> new for
>>>> us, so we will be slow.
>>>>
>>>> Any suggestions welcomed,
>>>>
>>>> Rob
>>>>
>>>> On 16 Dec 2015, at 16:54, Erik Jan de Wit wrote:
>>>>
>>>> Hi Rob,
>>>>
>>>> What you could try is to debug this in xcode, when the notification
>>>> is
>>>> touched it should launch the app and that will in turn call the JS
>>>> callback. Would be good to see if this code is called 100% of the
>>>> time.
>>>>
>>>> You can put a breakpoint here:
>>>>
>>>>
>> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AppDelegate%2Bnotification.m#L56
>>>>
>>>> That code will execute on cold start and here:
>>>>
>>>>
>> https://github.com/aerogear/aerogear-cordova-push/blob/master/src/ios/AGPushPlugin.m#L102
>>>>
>>>> That is where the onNotification callback gets invoked.
>>>>
>>>> Hope this helps,
>>>>
>>>> On Wed, Dec 16, 2015 at 5:14 PM, Rob Willett <
>>>> rob.aerogear at robertwillett.com
>>>>
>>>> wrote:
>>>>
>>>> Sebastien
>>>>
>>>> Yes, we do it at that point, $ionicPlatform.ready. I include the
>>>> whole of
>>>> that area of code for reference but we?re not expecting you to
>>>> debug it for
>>>> us. Merely to demonstrate its there.
>>>>
>>>> At the moment all we want the code to do is put an alert up.
>>>>
>>>> .run(function($ionicPlatform , CordovaService) {
>>>> $ionicPlatform.ready(function() {
>>>> if (window.StatusBar) {
>>>> // org.apache.cordova.statusbar required
>>>> StatusBar.styleDefault();
>>>> }
>>>>
>>>> ConsoleLog('<<< Cordova ready >>>');
>>>>
>>>> /* This seems to remove an annoying page flicker on iOS when the
>>>> keyboard
>>>> is displayed */
>>>> cordova.plugins.Keyboard.disableScroll(true);
>>>>
>>>> isDeviceReady = true;
>>>>
>>>> var uuid = "D26FBAF1-2EF2-4614-875F-4497EC4212D5/JFL1-0/ios_app";
>>>>
>>>> var aeroGearPushConfig = {
>>>> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>>>> ios: {
>>>> variantID: ?XXXXX?,
>>>> variantSecret: ?YYYYYYY?
>>>> } ,
>>>> // sendMetricInfo: true,
>>>> alias: uuid
>>>> };
>>>>
>>>> push.register(function (event) {
>>>> alert("EVENT = " + JSON.stringify(event));
>>>>
>>>> } , function () {
>>>> if (1)
>>>> {
>>>> // alert("AeroGearSuccessHandler: OK " + JSON.stringify(uuid));
>>>> // ConsoleLog("UUID = " + uuid);
>>>> }
>>>> } , function () {
>>>> } , aeroGearPushConfig);
>>>>
>>>> We were still loading up another 18,000 lines of code so we need to
>>>> start
>>>> pruning that back until we have something that works.
>>>>
>>>> Rob
>>>>
>>>> On 16 Dec 2015, at 16:04, Sebastien Blanc wrote:
>>>>
>>>> In the ionic app when do you do the registration of UPS ? on the
>>>> platformReady event ?
>>>>
>>>> On Wed, Dec 16, 2015 at 4:54 PM, Rob Willett <
>>>> rob.aerogear at robertwillett.com
>>>>
>>>> wrote:
>>>>
>>>> Erik,
>>>>
>>>> We have built the simplest possible app we can that uses the 
>>>> Aerogear
>>>> push plugin but using the ionic tabs starter kit.
>>>>
>>>> http://ionicframework.com/getting-started/
>>>>
>>>> We have taken the code directly from the Cordova simple app that we
>>>> have
>>>> got working and put it into the Ionic app.
>>>>
>>>> if we follow your tests as below:
>>>>
>>>> 1.
>>>>
>>>> IOS App in foreground, we send a simple push notification from the
>>>> Aerogear console - Works OK, We can see the event. Good
>>>> 2.
>>>>
>>>> IOS App in background, we send a simple push notification from the
>>>> Aerogear console - Works OK, We can see the event. Good
>>>> 3.
>>>>
>>>> IOS App killed, we send a simple push notification from the 
>>>> Aerogear
>>>>
>>>> console and some of the time when we click on the notification in 
>>>> the
>>>> notification drawer we do NOT get the notification handler called.
>>>> Not
>>>> so good
>>>>
>>>> However it does appear to work most of the time with our minimal
>>>> Ionic
>>>> app, but some of the time it fails. We had a run of 1 in 2 failures
>>>> when
>>>> we click on the notification. Now we have just done 20 runs in a 
>>>> row,
>>>> each time killing the app after receiving the notification and not 
>>>> a
>>>> single failure. Nothing changed.
>>>>
>>>> We cannot find any obvious reason for this so we are still
>>>> investigating.
>>>>
>>>> We have reconfigured our main app to work the same way as the 
>>>> minimal
>>>> app but we are still getting the same issues as before, we can see
>>>> the
>>>> notification in the drawer but clicking on it does NOT call the 
>>>> same
>>>> handler with the same code as the minimal app. We get zero calls to
>>>> the
>>>> notification event handler.
>>>>
>>>> We are wondering if there is a timing issue somewhere in our code,
>>>> but
>>>> we can?t see it. We also wondered if the size of the code we are
>>>> loading is the cause of a timing issue as well.
>>>>
>>>> Is there any way of adding more debugging into the Aerogear push
>>>> plugin
>>>> to see if we can track things down that way?
>>>>
>>>> Its very frustrating, but thanks for your help to date. It does 
>>>> look
>>>> like its an interaction with our code, Ionic and the Aerogear 
>>>> plugin.
>>>> My
>>>> money is on our code though. We?ll now start pulling working code
>>>> out
>>>> of our app until we get back to the minimal app. Only 18,604 lines 
>>>> to
>>>> go
>>>> :)
>>>>
>>>> Rob
>>>>
>>>> On 15 Dec 2015, at 10:36, Erik Jan de Wit wrote:
>>>>
>>>> Hi Rob,
>>>>
>>>> That would be a bug, although I can not reproduce it, to test it 
>>>> this
>>>> is
>>>> what I've done to test it:
>>>> $ > cordova create push-test <my bundle id>
>>>> $ > cordova platform add ios
>>>> $ > cordova plugin add aerogear-cordova-push
>>>>
>>>> copy paste your js code into www/js/index.js onDeviceReady, changed
>>>> pushServerUrl and variant info and changed quotes to " (this is 
>>>> your
>>>> email
>>>> client no doubt) and changed : into ; after console.log("Success")
>>>>
>>>> Attach Safari debugger and send a message when the app is in the
>>>> foreground
>>>> and get in the console:
>>>>
>>>> HandleAeroGearNotification: event =>
>>>>
>>>>
>>>>
>> {"alert":"test","foreground":true,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>>>>
>>>> I press the home button and send the app to the background send
>>>> another
>>>> message and 'touch' the message to launch the app:
>>>>
>>>> HandleAeroGearNotification: event =>
>>>>
>>>>
>>>>
>> {"alert":"background","foreground":false,"coldstart":false,"sound":"default","badge":-1,"payload":{}}
>>>>
>>>> The I kill the app by pressing home twice and swiping over the app 
>>>> to
>>>> remove it send another message and 'touch' it to launch the app. 
>>>> This
>>>> kills
>>>> my safari debugger so no way to see the console log, but in this 
>>>> case
>>>> coldstart should be true. To test this better changed the code to
>>>> alert
>>>> instead of console:
>>>>
>>>> function HandleAeroGearNotification(event) {
>>>> alert("HandleAeroGearNotification: event => " + event.coldstart);
>>>>
>>>> // Stuff cut for clarity
>>>> }
>>>>
>>>> I send another notification 'touch' it to launch the app and see 
>>>> the
>>>> alert
>>>> box display the text:
>>>>
>>>> HandleAeroGearNotification: event => true
>>>>
>>>> Hope this helps
>>>>
>>>> On Mon, Dec 14, 2015 at 10:20 PM, Rob Willett <
>>>> rob.aerogear at robertwillett.com> wrote:
>>>>
>>>> Hi,
>>>>
>>>> We think we have found a possible bug in the Aerogear Cordova 2.0.4
>>>> push
>>>> plugin specifically on the iOS side.
>>>> Summary
>>>>
>>>> We have two versions of our app, an Android and an IOS version. 
>>>> Both
>>>> use
>>>> the latest Cordova push plugin 2.0.4. They also both have the 
>>>> latest
>>>> Cordova platforms, android 4.1.1, ios 3.9.2. Both the iOS and 
>>>> Android
>>>> versions are compiled at the same time. We are running cordova 
>>>> 5.3.3
>>>> with
>>>> Ionic 1.7.8 (?).
>>>>
>>>> 1.
>>>>
>>>> We make sure that both apps are NOT started up on each device. We
>>>> also
>>>> check they are NOT in the background.
>>>> 2.
>>>>
>>>> We send the same simple notification to each device. This
>>>> notification
>>>> config is as below, we have anonymised the variants and alias in 
>>>> this
>>>> JSON
>>>> structure, though we can report that the UPS server sends the data
>>>> correctly. We use the additionalData flag to provide the 
>>>> information
>>>> necessary to decide which notification has been clicked in the
>>>> notification
>>>> drawer.
>>>>
>>>> 'variants' => [?variant1?,?variant2? ],
>>>> 'message' => {
>>>> 'additionalData' => { 'Disruption_Id' => '107546',
>>>> 'EpochTime' => '1450125268'
>>>> },
>>>> 'alert' => 'Cannon Street (EC4N) (All Directions) at the junction 
>>>> of
>>>> King William Street - To facilitate a heavy lift in Cannon Street,
>>>> Cannon Street will be closed. Traffic is slow moving on diversion.'
>>>> },
>>>> 'alias' => [ ?alias1? ],
>>>> 'ttl' => 600
>>>> };
>>>>
>>>> 1.
>>>>
>>>> Both devices show the message, the Android device stacks the 
>>>> message
>>>> and the iOS device display an individual message. This looks 
>>>> correct.
>>>> 2.
>>>>
>>>> Clicking on the Android stacked message starts up the app and the
>>>> Javascript notification handler we have defined,
>>>> HandleAeroGearNotification
>>>> is called
>>>>
>>>> HandleAeroGearNotification: event => {"alert":"Cannon Street (EC4N)
>>>> (All Directions) at the junction of King William Street - To
>>>> facilitate a heavy lift in Cannon Street, Cannon Street will be
>>>> closed. Traffic is slow moving on
>>>>
>>>>
>> diversion.","coldstart":true,"foreground":true,"payload":{"alert":"Cannon
>>>>
>>>> Street (EC4N) (All Directions) at the junction of King William 
>>>> Street
>>>> - To facilitate a heavy lift in Cannon Street, Cannon Street will 
>>>> be
>>>> closed. Traffic is slow moving on diversion.","badge":"-1"}}
>>>>
>>>> 1.
>>>>
>>>> Clicking on the notification in the notification drawer on the iOS
>>>> device also starts our app up correctly but the notification 
>>>> handler,
>>>> HandleAeroGearNotification(), is NOT called. The app starts up as
>>>> normal as
>>>> if the notification had not been clicked. We would expect the
>>>> notification
>>>> handler to be called in iOS as it is in Android.
>>>> 2.
>>>>
>>>> All notifications are cleared on both Android and iOS correctly 
>>>> when
>>>> the app is started up.
>>>> 3.
>>>>
>>>> We define HandleAeroGearNotification as
>>>>
>>>> var aeroGearPushConfig = {
>>>> pushServerURL: "https://push-jambuster.rhcloud.com/ag-push/",
>>>> ios: {
>>>> variantID: ?variantid_obscured?,
>>>> variantSecret: ?variant_secret_obscured?
>>>> } ,
>>>> android: {
>>>> senderID: "variantid_obscured" ,
>>>> variantID: "variant_id_obscured" ,
>>>> variantSecret: "variant_secret_obscured"
>>>> } ,
>>>> sendMetricInfo: true,
>>>> alias: alias1
>>>> };
>>>>
>>>> function HandleAeroGearNotification(event) {
>>>> console.log(?HandleAeroGearNotification: event => ? +
>>>> JSON.stringify(event));
>>>>
>>>> // Stuff cut for clarity
>>>> }
>>>>
>>>> // Slightly simplified registration event.
>>>> push.register(HandleAeroGearNotification , function () {
>>>> console.log(?Success?):
>>>> } , function () {
>>>> console.log(?Failure?);
>>>> } , aeroGearPushConfig);
>>>>
>>>> We cannot see any reference to this issue in the JIRA database and
>>>> wondered if it is a bug or not.
>>>>
>>>> If its a bug we are happy to raise it accordingly.
>>>>
>>>> Please let us know,
>>>>
>>>> Thanks
>>>> Rob
>>>>
>>>> Aerogear-users mailing list
>>>> Aerogear-users at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>>
>>>> --
>>>> Cheers,
>>>> Erik Jan
>>>>
>>>> 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
>>>> ------------------------------
>>>>
>>>> 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
>>>>
>>>> --
>>>> Cheers,
>>>> Erik Jan
>>>> ------------------------------
>>>>
>>>> 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
>>>>
>>>> ------------------------------
>>>>
>>>> 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
>>>>
>>>>
>>>
>>>
>>> --
>>> Cheers,
>>>  Erik Jan
>>> _______________________________________________
>>> 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
>>
>
>
>
> -- 
> Cheers,
>     Erik Jan
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users


From matzew at apache.org  Wed Jan 13 10:57:06 2016
From: matzew at apache.org (Matthias Wessendorf)
Date: Wed, 13 Jan 2016 16:57:06 +0100
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Feature request: make
 deleteOutdatedPushInformationData configurable
In-Reply-To: <CAAg5f2R2PYNxz1xf6T0ZXTiC6ss23eU6WApdiEZA351f+ffHqA@mail.gmail.com>
References: <1452516690190-419.post@n5.nabble.com>
	<CAAg5f2Sj6nFQDT4360M66916fspDMNDE4eyJzKY0uC+BbJYkNA@mail.gmail.com>
	<1452590423299-425.post@n5.nabble.com>
	<CAAg5f2R2PYNxz1xf6T0ZXTiC6ss23eU6WApdiEZA351f+ffHqA@mail.gmail.com>
Message-ID: <CAAg5f2RHp1pZB6WHaexh1YUDrnzNdOW3fNE5MJ4evM7ucY5GCQ@mail.gmail.com>

https://github.com/aerogear/aerogear-unifiedpush-server/pull/670

@Guenter, it won't make it into the 1.1.x series

However, no big deal for us to run a 1.2.0-alpha.1 somewhat soon - there
was some talks about that on our dev list as well...

-M

On Tue, Jan 12, 2016 at 10:54 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> cool, will do.
>
> PR will come soon ;)
>
>
> On Tuesday, 12 January 2016, gklein <gunther.klein at f24.com> wrote:
>
>> Hi!
>>
>> Thanks for your replies. I think a system property would be perferrable
>> and
>> sufficient in our case. Additional ui support is nice to have.
>>
>> Can you file the jira ticket for me please. I would have to sign up first.
>> Here is the description:
>> ----
>>
>> Aerogear UPS 1.1.0 collects outdated push message infos in a batch job
>> (calls to PushMessageMetricsService#deleteOutdatedPushInformationData).
>> The
>> outdated criteria is currently hardcoded to 30 days
>> (PushMessageMetricsService#DAYS_OF_MAX_OLDEST_INFO_MSG). This time should
>> be
>> made configurable via system property. If the system property is not set
>> the
>> default value (30 days) should be used.
>>
>> ---
>>
>> Regards, Gunther Klein
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Feature-request-make-deleteOutdatedPushInformationData-configurable-tp419p425.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>
>
> --
> Sent from Gmail Mobile
>



-- 
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/20160113/17333c71/attachment.html 

From gunther.klein at f24.com  Thu Jan 14 13:33:50 2016
From: gunther.klein at f24.com (gklein)
Date: Thu, 14 Jan 2016 11:33:50 -0700 (MST)
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Severe TTL Bug for APNS
Message-ID: <1452796430138-435.post@n5.nabble.com>

Hi!

We specified a value of 3600 (1 hour) for the ttl field in the push message
structure. We detected that in case of iOs devices, that were offline just a
short time (e.g. 20 seconds) no pushes were received. For android everything
seems fine. 
Looking at the code (APNsPushNotificationSender#createFutureDateBasedOnTTL)
we can see that the expiry date seems to be computed incorrectly: 
---
 return new Date(System.currentTimeMillis() + ttl);
---
ttl is the time-to-live in seconds. In this case ttl should be multiplied
with 1000!

So this explains our symptoms. Or am i missing anything here?

Further question/issue: When specifying ttl=-1 we detected, that our ios
device also didn't receive any push notifications  after some short time
beeing offline. Can anybody explain why? We thought apns would store the
push message for several weeks in that case. When the device was online we
however successfully received pushes with ttl=-1. Any clue whats going on
here?

p.s.: our message looks something like that:
---
{"message":{"badge":1,"alert":"You have new
messages","sound":"NotificationSound.aiff","user-data":{"room_id":"77bf84a5aa254da0b916bc0e7b0f1f7d","type":"message"},"apns":{"content-available":true}},"criteria":{"alias":["HGEUZTM7"]},"config":{"ttl":-1}}
---

Regards, Gunther Klein








--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Severe-TTL-Bug-for-APNS-tp435.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From gunther.klein at f24.com  Mon Jan 18 04:28:52 2016
From: gunther.klein at f24.com (gklein)
Date: Mon, 18 Jan 2016 02:28:52 -0700 (MST)
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Several Severe TTL Bugs
	for APNS
In-Reply-To: <1452796430138-435.post@n5.nabble.com>
References: <1452796430138-435.post@n5.nabble.com>
Message-ID: <1453109332618-436.post@n5.nabble.com>

Hi!

Did anybody have a look at this yet? I mean these are severe bugs!



Regards, Gunther Klein



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Several-Severe-TTL-Bugs-for-APNS-tp435p436.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Mon Jan 18 06:04:57 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 18 Jan 2016 12:04:57 +0100
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Several Severe TTL Bugs
	for APNS
In-Reply-To: <1453109332618-436.post@n5.nabble.com>
References: <1452796430138-435.post@n5.nabble.com>
	<1453109332618-436.post@n5.nabble.com>
Message-ID: <CAD_dpu0TyJUNf=2etuEL1ciW=poUJroOEAAEkVnWBNCWoOHuMA@mail.gmail.com>

Hi Gunther !

You are absolutly right, and created a ticket with critical status
https://issues.jboss.org/browse/AGPUSH-1567 and the fix will be shipped in
our (soon to be released) 1.1.1 release.

Seb


On Mon, Jan 18, 2016 at 10:28 AM, gklein <gunther.klein at f24.com> wrote:

> Hi!
>
> Did anybody have a look at this yet? I mean these are severe bugs!
>
>
>
> Regards, Gunther Klein
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Several-Severe-TTL-Bugs-for-APNS-tp435p436.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160118/fb846060/attachment.html 

From gunther.klein at f24.com  Mon Jan 18 06:47:28 2016
From: gunther.klein at f24.com (gklein)
Date: Mon, 18 Jan 2016 04:47:28 -0700 (MST)
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Several Severe TTL Bugs
 for APNS
In-Reply-To: <CAD_dpu0TyJUNf=2etuEL1ciW=poUJroOEAAEkVnWBNCWoOHuMA@mail.gmail.com>
References: <1452796430138-435.post@n5.nabble.com>
	<1453109332618-436.post@n5.nabble.com>
	<CAD_dpu0TyJUNf=2etuEL1ciW=poUJroOEAAEkVnWBNCWoOHuMA@mail.gmail.com>
Message-ID: <1453117648376-438.post@n5.nabble.com>

Hi Sebastian!

Thanks for your answer. 
Please note also the other bug when sending -1 as ttl
(https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L201).
I think its discussable if this represents a bug in the apns java lib or on
aerogear side. Fact is however that it is severe and prevents messages from
beeing persistet on apns at all. Aerogear code could workaround it very
easily like that:

--- instead of ----
 return new Date(System.currentTimeMillis() +
EnhancedApnsNotification.MAXIMUM_EXPIRY * 1000L);
---- should change to ---
return new Date(EnhancedApnsNotification.MAXIMUM_EXPIRY * 1000L);
---
Anything bigger than 'EnhancedApnsNotification.MAXIMUM_EXPIRY * 1000L' will
result in negative values sent to apns!

Regards, Gunther Klein




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Several-Severe-TTL-Bugs-for-APNS-tp435p438.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From scm.blanc at gmail.com  Mon Jan 18 11:02:09 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Mon, 18 Jan 2016 17:02:09 +0100
Subject: [Aerogear-users] Aerogear UPS 1.1.0: Several Severe TTL Bugs
	for APNS
In-Reply-To: <1453117648376-438.post@n5.nabble.com>
References: <1452796430138-435.post@n5.nabble.com>
	<1453109332618-436.post@n5.nabble.com>
	<CAD_dpu0TyJUNf=2etuEL1ciW=poUJroOEAAEkVnWBNCWoOHuMA@mail.gmail.com>
	<1453117648376-438.post@n5.nabble.com>
Message-ID: <CAD_dpu1Z0Zo4en2KAgv+3hnOenXmKN2WOQhbZ5aYb-VtSkwWyg@mail.gmail.com>

Thanks,
I've updated the ticket, we will fix both


On Mon, Jan 18, 2016 at 12:47 PM, gklein <gunther.klein at f24.com> wrote:

> Hi Sebastian!
>
> Thanks for your answer.
> Please note also the other bug when sending -1 as ttl
> (
> https://github.com/aerogear/aerogear-unifiedpush-server/blob/master/push/sender/src/main/java/org/jboss/aerogear/unifiedpush/message/sender/APNsPushNotificationSender.java#L201
> ).
> I think its discussable if this represents a bug in the apns java lib or on
> aerogear side. Fact is however that it is severe and prevents messages from
> beeing persistet on apns at all. Aerogear code could workaround it very
> easily like that:
>
> --- instead of ----
>  return new Date(System.currentTimeMillis() +
> EnhancedApnsNotification.MAXIMUM_EXPIRY * 1000L);
> ---- should change to ---
> return new Date(EnhancedApnsNotification.MAXIMUM_EXPIRY * 1000L);
> ---
> Anything bigger than 'EnhancedApnsNotification.MAXIMUM_EXPIRY * 1000L' will
> result in negative values sent to apns!
>
> Regards, Gunther Klein
>
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-1-1-0-Several-Severe-TTL-Bugs-for-APNS-tp435p438.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160118/015e34a6/attachment.html 

From aamagdi at ejada.com  Mon Jan 18 11:51:52 2016
From: aamagdi at ejada.com (aamagdi)
Date: Mon, 18 Jan 2016 09:51:52 -0700 (MST)
Subject: [Aerogear-users] Aerogear UPS Deployment to Oracle Database
Message-ID: <1453135912123-440.post@n5.nabble.com>

Hi

I was trying to enable UPS server to work with Oracle database, I will
operation goes fine except adding new iOS variant, I check table
*IOS_VARIANT* and found that column *CERT_DATA* was *varchar2(4000)* so it
is long enough for certification file data I changed it to *CLOB* type but
when starting the server hibernate check is complaining about colum type and
gave the below exception

*2016-01-18 19:44:08,267 ERROR [org.jboss.msc.service.fail] (ServerService
Thread Pool -- 62) MSC000001: Failed to start service
jboss.persistenceunit."unifiedpush-server-wildfly.war#unifiedpush-default":
org.jboss.msc.service.StartException in service
jboss.persistenceunit."unifiedpush-server-wildfly.war#unifiedpush-default":
org.hibernate.HibernateException: Wrong column type in
UNIFIEDPUSH.IOS_VARIANT for column cert_data. Found: clob, expected: long
	at
org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:172)
[wildfly-jpa-8.2.1.Final.jar:8.2.1.Final]*

I changed the column type to *LONG*, server started fine but when trying to
add new iOS variant I ma getting the below exception, I checked the database
*IOS_VARIANT* record has been created and *VARIANT* recored created but
*PUSH_APPLICATION_ID* was empty, even after setting *PUSH_APPLICATION_ID*
manually it failed in variants inquiry, could you please advise.

*command : org.hibernate.exception.GenericJDBCException: Could not read
entity state from ResultSet :
EntityKey[org.jboss.aerogear.unifiedpush.api.Variant#ec4df739-8f89-421a-8bad-4f1e72fcb7f8]
2016-01-18 19:36:40,664 ERROR [org.jboss.as.ejb3.invocation] (default
task-27) JBAS014134: EJB Invocation failed on component
PushApplicationServiceImpl for method public abstract void
org.jboss.aerogear.unifiedpush.service.PushApplicationService.addVariant(org.jboss.aerogear.unifiedpush.api.PushApplication,org.jboss.aerogear.unifiedpush.api.Variant):
javax.ejb.EJBException: javax.persistence.PersistenceException:
org.hibernate.exception.GenericJDBCException: Could not read entity state
from ResultSet :
EntityKey[org.jboss.aerogear.unifiedpush.api.Variant#ec4df739-8f89-421a-8bad-4f1e72fcb7f8]
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.handleExceptionInOurTx(CMTTxInterceptor.java:190)
[wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final]
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.invokeInOurTx(CMTTxInterceptor.java:275)
[wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final]
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.required(CMTTxInterceptor.java:340)
[wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final]
	at
org.jboss.as.ejb3.tx.CMTTxInterceptor.processInvocation(CMTTxInterceptor.java:239)
[wildfly-ejb3-8.2.1.Final.jar:8.2.1.Final]
	at
org.jboss.invocation.InterceptorContext.proceed(InterceptorContext.java:309)
	at 
.
.
.
Caused by: java.sql.SQLException: Stream has already been closed
	at oracle.jdbc.driver.LongAccessor.getBytesInternal(LongAccessor.java:156)
	at oracle.jdbc.driver.LongAccessor.getBytes(LongAccessor.java:126)
	at oracle.jdbc.driver.LongAccessor.getString(LongAccessor.java:201)
	at oracle.jdbc.driver.T4CLongAccessor.getString(T4CLongAccessor.java:450)
	at
oracle.jdbc.driver.OracleResultSetImpl.getString(OracleResultSetImpl.java:1297)
	at oracle.jdbc.driver.OracleResultSet.getString(OracleResultSet.java:494)
	at
org.jboss.jca.adapters.jdbc.WrappedResultSet.getString(WrappedResultSet.java:1381)
	at
org.hibernate.type.descriptor.sql.VarcharTypeDescriptor$2.doExtract(VarcharTypeDescriptor.java:74)
[hibernate-core-4.3.7.Final.jar:4.3.7.Final]
	at
org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64)
[hibernate-core-4.3.7.Final.jar:4.3.7.Final]
	at
org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:267)
[hibernate-core-4.3.7.Final.jar:4.3.7.Final]*

Thanks



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-UPS-Deployment-to-Oracle-Database-tp440.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From aamagdi at ejada.com  Tue Jan 19 06:21:54 2016
From: aamagdi at ejada.com (aamagdi)
Date: Tue, 19 Jan 2016 04:21:54 -0700 (MST)
Subject: [Aerogear-users] Aerogear Cordova Push Plugin Android Issue
Message-ID: <1453202514030-441.post@n5.nabble.com>

Hi,

I tried to send a push notification message using the rest sender api as
below
{"message": {
  "alert": "test123",
   "user-data": {  
            "somedata":"0",
            "somedata2":"1234"
   }
}}
if the application in the foreground I can read the "user-date" correctly
under the payload object on the notification received call back, but if the
application wasn't in the foreground the object doesn't contain the payload
data ("user-date").

I make a quick review of the plugin code for Android and found that in this
part 
NotificationMessageHandler.java -> line 77 (Message message = new
Message(extras);) you are creating a new message object from the extras
variable ;that have all the data; then in
Message.java -> line 46 in the class constructor
    public Message(Bundle extras) {
        this(extras.getString("alert"), extras.getString("sound"),
                Integer.parseInt(extras.getString("badge")),
                extras.getString("aerogear-push-id"),
                *extras.getBundle("userData"));*
    }
there is not "userData" field under extras, so this will result of ignoring
all other payload data.

Could you please check it



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-Cordova-Push-Plugin-Android-Issue-tp441.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From edewit at redhat.com  Tue Jan 19 09:22:01 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 19 Jan 2016 15:22:01 +0100
Subject: [Aerogear-users] Duplicated notifications
In-Reply-To: <CAAg5f2RAMNGDbp6Ga_Y_q3pw+th=TaayY-kqeqctwVDe2q9WGA@mail.gmail.com>
References: <56697CCA.3090006@udl.cat>
	<CAAg5f2RAMNGDbp6Ga_Y_q3pw+th=TaayY-kqeqctwVDe2q9WGA@mail.gmail.com>
Message-ID: <CAO2B-fagaf0KNWfHoCtt63rdYJ=JmYkAazSf_ga7O0vw-dM96A@mail.gmail.com>

Sorry for the even later reply, but could it be that you have one device
that is registered multiple times?

On Thu, Dec 17, 2015 at 11:05 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi Alex,
>
> sorry for the late reply, can you file a JIRA for AGCORDOVA ?
>
> On Thu, Dec 10, 2015 at 2:23 PM, Alex Ballest? <alexandre.balleste at udl.cat
> > wrote:
>
>> Hi, recently I've updated to 2.0.4 cordova plugin and I noticed that lot
>> of times notifications are not displayed. Others the notifications are
>> displayed multiple times in the bar but it was only sent once, and others
>> times are shown with some older that I've already received. Any suggestion
>> to find what's happening?
>>
>> Things already detected: If APP is closed I've see the notification with
>> "1" number. If opened I see it with an "8" .
>>
>> Screenshots:
>>
>> http://ibin.co/2PTCBCRewjEx
>> http://ibin.co/2PTCPYtIqiJy
>>
>> Following the stacktrace of the last message sent:
>> http://pastebin.com/FtFr6fbc
>>
>> Thanks
>>
>> Alex.
>>
>> --
>>
>> Alexandre Ballest? Crevill?n alexandre.balleste at udl.cat
>> ====================
>> Universitat de Lleida
>>
>> ?rea de sistemes d'Informaci? i Comunicacions
>>
>> Analista/Programador
>>
>> University of Lleida
>>
>> Information and Communication Systems Service
>>
>> Tlf: +34 973 702148
>>
>> Fax: +34 973 702130
>>
>> =====================
>>
>> Av?s legal/Aviso legal/Avertiment legal/Legal notice
>> <http://www.imatge.udl.cat/avis_legal_lopd.html>
>>
>> _______________________________________________
>> 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
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160119/37a2eddc/attachment.html 

From edewit at redhat.com  Tue Jan 19 12:25:06 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 19 Jan 2016 18:25:06 +0100
Subject: [Aerogear-users] Aerogear Cordova Push Plugin Android Issue
In-Reply-To: <1453202514030-441.post@n5.nabble.com>
References: <1453202514030-441.post@n5.nabble.com>
Message-ID: <CAO2B-famZgcgRMsi-VSTGwWMN3VSr_52Wfr4AN0S58PZggyS4w@mail.gmail.com>

Yes this is an error in the plugin, actually 2 errors it's not a bundle (it
should be a string) and it's not called userData (but user-data).

On Tue, Jan 19, 2016 at 12:21 PM, aamagdi <aamagdi at ejada.com> wrote:

> Hi,
>
> I tried to send a push notification message using the rest sender api as
> below
> {"message": {
>   "alert": "test123",
>    "user-data": {
>             "somedata":"0",
>             "somedata2":"1234"
>    }
> }}
> if the application in the foreground I can read the "user-date" correctly
> under the payload object on the notification received call back, but if the
> application wasn't in the foreground the object doesn't contain the payload
> data ("user-date").
>
> I make a quick review of the plugin code for Android and found that in this
> part
> NotificationMessageHandler.java -> line 77 (Message message = new
> Message(extras);) you are creating a new message object from the extras
> variable ;that have all the data; then in
> Message.java -> line 46 in the class constructor
>     public Message(Bundle extras) {
>         this(extras.getString("alert"), extras.getString("sound"),
>                 Integer.parseInt(extras.getString("badge")),
>                 extras.getString("aerogear-push-id"),
>                 *extras.getBundle("userData"));*
>     }
> there is not "userData" field under extras, so this will result of ignoring
> all other payload data.
>
> Could you please check it
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Aerogear-Cordova-Push-Plugin-Android-Issue-tp441.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160119/f7419dfb/attachment.html 

From edewit at redhat.com  Tue Jan 19 12:45:10 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Tue, 19 Jan 2016 18:45:10 +0100
Subject: [Aerogear-users] Aerogear Cordova Push Plugin Android Issue
In-Reply-To: <CAO2B-famZgcgRMsi-VSTGwWMN3VSr_52Wfr4AN0S58PZggyS4w@mail.gmail.com>
References: <1453202514030-441.post@n5.nabble.com>
	<CAO2B-famZgcgRMsi-VSTGwWMN3VSr_52Wfr4AN0S58PZggyS4w@mail.gmail.com>
Message-ID: <CAO2B-fbjf7ctA=c9=KdsqeUVRYPdW2kK=ZSmqAerniAw-vVcrg@mail.gmail.com>

fixed the issue:
https://issues.jboss.org/browse/AGCORDOVA-132

pr:
https://github.com/aerogear/aerogear-cordova-push/pull/90

if you like you could try it out

On Tue, Jan 19, 2016 at 6:25 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Yes this is an error in the plugin, actually 2 errors it's not a bundle
> (it should be a string) and it's not called userData (but user-data).
>
> On Tue, Jan 19, 2016 at 12:21 PM, aamagdi <aamagdi at ejada.com> wrote:
>
>> Hi,
>>
>> I tried to send a push notification message using the rest sender api as
>> below
>> {"message": {
>>   "alert": "test123",
>>    "user-data": {
>>             "somedata":"0",
>>             "somedata2":"1234"
>>    }
>> }}
>> if the application in the foreground I can read the "user-date" correctly
>> under the payload object on the notification received call back, but if
>> the
>> application wasn't in the foreground the object doesn't contain the
>> payload
>> data ("user-date").
>>
>> I make a quick review of the plugin code for Android and found that in
>> this
>> part
>> NotificationMessageHandler.java -> line 77 (Message message = new
>> Message(extras);) you are creating a new message object from the extras
>> variable ;that have all the data; then in
>> Message.java -> line 46 in the class constructor
>>     public Message(Bundle extras) {
>>         this(extras.getString("alert"), extras.getString("sound"),
>>                 Integer.parseInt(extras.getString("badge")),
>>                 extras.getString("aerogear-push-id"),
>>                 *extras.getBundle("userData"));*
>>     }
>> there is not "userData" field under extras, so this will result of
>> ignoring
>> all other payload data.
>>
>> Could you please check it
>>
>>
>>
>> --
>> View this message in context:
>> http://aerogear-users.1116366.n5.nabble.com/Aerogear-Cordova-Push-Plugin-Android-Issue-tp441.html
>> Sent from the aerogear-users mailing list archive at Nabble.com.
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>
>
>
> --
> Cheers,
>        Erik Jan
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160119/f9ff14d6/attachment.html 

From alexandre.balleste at udl.cat  Wed Jan 20 02:04:37 2016
From: alexandre.balleste at udl.cat (=?windows-1252?Q?Alex_Ballest=E9?=)
Date: Wed, 20 Jan 2016 08:04:37 +0100
Subject: [Aerogear-users] Duplicated notifications
In-Reply-To: <CAO2B-fagaf0KNWfHoCtt63rdYJ=JmYkAazSf_ga7O0vw-dM96A@mail.gmail.com>
References: <56697CCA.3090006@udl.cat>	<CAAg5f2RAMNGDbp6Ga_Y_q3pw+th=TaayY-kqeqctwVDe2q9WGA@mail.gmail.com>
	<CAO2B-fagaf0KNWfHoCtt63rdYJ=JmYkAazSf_ga7O0vw-dM96A@mail.gmail.com>
Message-ID: <569F3185.3070100@udl.cat>

May be is something related with registering the device multiple times. 
When I've downgraded to 2.0.3 it worked fine again. In three weeks I'll 
have time to try to use 2.0.4 again and see what was happening.

Alex.

El 19/01/16 a les 15:22, Erik Jan de Wit ha escrit:
> Sorry for the even later reply, but could it be that you have one 
> device that is registered multiple times?
>
> On Thu, Dec 17, 2015 at 11:05 AM, Matthias Wessendorf 
> <matzew at apache.org <mailto:matzew at apache.org>> wrote:
>
>     Hi Alex,
>
>     sorry for the late reply, can you file a JIRA for AGCORDOVA ?
>
>     On Thu, Dec 10, 2015 at 2:23 PM, Alex Ballest?
>     <alexandre.balleste at udl.cat <mailto:alexandre.balleste at udl.cat>>
>     wrote:
>
>         Hi, recently I've updated to 2.0.4 cordova plugin and I
>         noticed that lot of times notifications are not displayed.
>         Others the notifications are displayed multiple times in the
>         bar but it was only sent once, and others times are shown with
>         some older that I've already received. Any suggestion to find
>         what's happening?
>
>         Things already detected: If APP is closed I've see the
>         notification with "1" number. If opened I see it with an "8" .
>
>         Screenshots:
>
>         http://ibin.co/2PTCBCRewjEx
>         http://ibin.co/2PTCPYtIqiJy
>
>         Following the stacktrace of the last message sent:
>         http://pastebin.com/FtFr6fbc
>
>         Thanks
>
>         Alex.
>
>         -- 
>
>         Alexandre Ballest? Crevill?n alexandre.balleste at udl.cat
>         <http://udl.cat>
>         ====================
>         Universitat de Lleida
>
>         ?rea de sistemes d'Informaci? i Comunicacions
>
>         Analista/Programador
>
>
>         University of Lleida
>
>         Information and Communication Systems Service
>
>
>         Tlf: +34 973 702148 <tel:%2B34%20973%20702148>
>
>         Fax: +34 973 702130 <tel:%2B34%20973%20702130>
>
>         =====================
>
>         Av?s legal/Aviso legal/Avertiment legal/Legal notice
>         <http://www.imatge.udl.cat/avis_legal_lopd.html>
>
>
>         _______________________________________________
>         Aerogear-users mailing list
>         Aerogear-users at lists.jboss.org
>         <mailto: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 <mailto:Aerogear-users at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
>
> -- 
> Cheers,
>        Erik Jan
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users


-- 

Alexandre Ballest? Crevill?n alexandre.balleste at udl.cat
====================
Universitat de Lleida

?rea de sistemes d'Informaci? i Comunicacions

Analista/Programador


University of Lleida

Information and Communication Systems Service


Tlf: +34 973 702148

Fax: +34 973 702130

=====================

Av?s legal/Aviso legal/Avertiment legal/Legal notice 
<http://www.imatge.udl.cat/avis_legal_lopd.html>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160120/8e87dd09/attachment-0001.html 

From kurrent93 at gmail.com  Thu Jan 21 13:52:14 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 19:52:14 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
Message-ID: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>

Hello

I am trying to get started with Cordova and Aerogear push.

When I try to run a simple cordova app I get the following:
!JavaScript ERROR: Plugin PushPlugin.messageChannel is not supported
!JavaScript ERROR: Plugin PushPlugin.register is not supported

How then do you test that the push is working?

Second question - apologies if this sounds dumb - am completely new to
mobile. Can a push message contain json or xml, or does it have to be
simple text?

Thanks
Anton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/03d9e709/attachment.html 

From lholmqui at redhat.com  Thu Jan 21 13:55:15 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 13:55:15 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
Message-ID: <CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>

Hello

On Thu, Jan 21, 2016 at 1:52 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Hello
>
> I am trying to get started with Cordova and Aerogear push.
>
> When I try to run a simple cordova app I get the following:
>
 Are you following along on the Aerogear.org tutorials or something else?

> !JavaScript ERROR: Plugin PushPlugin.messageChannel is not supported
> !JavaScript ERROR: Plugin PushPlugin.register is not supported
>
> How then do you test that the push is working?
>
> Second question - apologies if this sounds dumb - am completely new to
> mobile. Can a push message contain json or xml, or does it have to be
> simple text?
>
> Thanks
> Anton
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/3ddb1db8/attachment.html 

From kurrent93 at gmail.com  Thu Jan 21 14:05:06 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 20:05:06 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
Message-ID: <CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>

On Thu, Jan 21, 2016 at 7:55 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>  Are you following along on the Aerogear.org tutorials or something else?


Yes sir.
Unfortunately the sample for the aerodoc cordova project is now a broken
link - https://aerogear.org/getstarted/demos/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/ac46a9d7/attachment.html 

From lholmqui at redhat.com  Thu Jan 21 14:12:58 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 14:12:58 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
Message-ID: <CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>

On Thu, Jan 21, 2016 at 2:05 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Thu, Jan 21, 2016 at 7:55 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>>  Are you following along on the Aerogear.org tutorials or something else?
>
>
> Yes sir.
> Unfortunately the sample for the aerodoc cordova project is now a broken
> link - https://aerogear.org/getstarted/demos/
>
that is odd.


perhaps try this example. should be less involved than aerodoc,  just
focusing on push

https://github.com/aerogear/aerogear-cordova-push

>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/a4dbce83/attachment.html 

From dpassos at redhat.com  Thu Jan 21 14:17:50 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 21 Jan 2016 17:17:50 -0200
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
Message-ID: <CADF=h2vw0p51wYBoCyzYLfZ4aU_fyiU4x-RmT6KC=mtKPFp3Yg@mail.gmail.com>

You can try using this. =>
https://github.com/jboss-mobile/unified-push-helloworld/tree/master/cordova

On Thu, Jan 21, 2016 at 5:12 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Thu, Jan 21, 2016 at 2:05 PM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>>
>> On Thu, Jan 21, 2016 at 7:55 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>  Are you following along on the Aerogear.org tutorials or something else?
>>
>>
>> Yes sir.
>> Unfortunately the sample for the aerodoc cordova project is now a broken
>> link - https://aerogear.org/getstarted/demos/
>>
> that is odd.
>
>
> perhaps try this example. should be less involved than aerodoc,  just
> focusing on push
>
> https://github.com/aerogear/aerogear-cordova-push
>
>>
>> _______________________________________________
>> 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
>
>


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/adb290cc/attachment.html 

From kurrent93 at gmail.com  Thu Jan 21 14:39:44 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 20:39:44 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
Message-ID: <CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>

On Thu, Jan 21, 2016 at 8:12 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> perhaps try this example. should be less involved than aerodoc,  just
> focusing on push
>
> https://github.com/aerogear/aerogear-cordova-push
>

Thank you. That helped. The error is now gone. But, I still do not get any
notifications.

When I run the sample app, I notice that the deviceready event never seems
to be called, even when I call it from the cordova ui.

[image: Inline image 1]

Where do I find an example of the config.xml?

Thanks for your help!!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/b812a3ab/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 101311 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/b812a3ab/attachment-0001.png 

From lholmqui at redhat.com  Thu Jan 21 14:43:14 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 14:43:14 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
Message-ID: <CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>

i believe you will need to be on a real device to receive a push message.



On Thu, Jan 21, 2016 at 2:39 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Thu, Jan 21, 2016 at 8:12 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> perhaps try this example. should be less involved than aerodoc,  just
>> focusing on push
>>
>> https://github.com/aerogear/aerogear-cordova-push
>>
>
> Thank you. That helped. The error is now gone. But, I still do not get any
> notifications.
>
> When I run the sample app, I notice that the deviceready event never seems
> to be called, even when I call it from the cordova ui.
>
> [image: Inline image 1]
>
> Where do I find an example of the config.xml?
>
> Thanks for your help!!
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/f2e7157c/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 101311 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/f2e7157c/attachment-0001.png 

From kurrent93 at gmail.com  Thu Jan 21 14:48:07 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 20:48:07 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
Message-ID: <CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>

On Thu, Jan 21, 2016 at 8:43 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> i believe you will need to be on a real device to receive a push message.
>

Really? That will make development very slow if you need to deploy to a
real device to test push.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/927e6f3b/attachment.html 

From lholmqui at redhat.com  Thu Jan 21 14:50:00 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 14:50:00 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
Message-ID: <CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>

On Thu, Jan 21, 2016 at 2:48 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Thu, Jan 21, 2016 at 8:43 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> i believe you will need to be on a real device to receive a push message.
>>
>
> Really? That will make development very slow if you need to deploy to a
> real device to test push.
>
yea,  it kind of sucks,  but that is the reality

>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/7298eadd/attachment.html 

From kurrent93 at gmail.com  Thu Jan 21 15:01:15 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 21:01:15 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
Message-ID: <CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>

Ok. And is a push notification only meant to be a string?

If I want to push a complex message to a specific client, is push the right
approach - or is there something else I should look at?

On Thu, Jan 21, 2016 at 8:50 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Thu, Jan 21, 2016 at 2:48 PM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>>
>> On Thu, Jan 21, 2016 at 8:43 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> i believe you will need to be on a real device to receive a push message.
>>>
>>
>> Really? That will make development very slow if you need to deploy to a
>> real device to test push.
>>
> yea,  it kind of sucks,  but that is the reality
>
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/12af20d8/attachment.html 

From lholmqui at redhat.com  Thu Jan 21 15:03:25 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 15:03:25 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>
Message-ID: <CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>

both android and iOS have limitations on the message payload,  so the
message is usually just a string.

On Thu, Jan 21, 2016 at 3:01 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Ok. And is a push notification only meant to be a string?
>
> If I want to push a complex message to a specific client, is push the
> right approach - or is there something else I should look at?
>
> On Thu, Jan 21, 2016 at 8:50 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>>
>> On Thu, Jan 21, 2016 at 2:48 PM, Anton Hughes <kurrent93 at gmail.com>
>> wrote:
>>
>>>
>>> On Thu, Jan 21, 2016 at 8:43 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> i believe you will need to be on a real device to receive a push
>>>> message.
>>>>
>>>
>>> Really? That will make development very slow if you need to deploy to a
>>> real device to test push.
>>>
>> yea,  it kind of sucks,  but that is the reality
>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/f7dd89bd/attachment.html 

From lholmqui at redhat.com  Thu Jan 21 15:03:44 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 15:03:44 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>
	<CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>
Message-ID: <CALD3Fd088UYLfVAmsoUJKrL2vO=+MBsx5HSx1YR+Q58jsyg_Cw@mail.gmail.com>

On Thu, Jan 21, 2016 at 3:03 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> both android and iOS have limitations on the message payload,  so the
> message is usually just a string.
>
message payload size that should be

>
> On Thu, Jan 21, 2016 at 3:01 PM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>> Ok. And is a push notification only meant to be a string?
>>
>> If I want to push a complex message to a specific client, is push the
>> right approach - or is there something else I should look at?
>>
>> On Thu, Jan 21, 2016 at 8:50 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Thu, Jan 21, 2016 at 2:48 PM, Anton Hughes <kurrent93 at gmail.com>
>>> wrote:
>>>
>>>>
>>>> On Thu, Jan 21, 2016 at 8:43 PM, Luke Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>> i believe you will need to be on a real device to receive a push
>>>>> message.
>>>>>
>>>>
>>>> Really? That will make development very slow if you need to deploy to a
>>>> real device to test push.
>>>>
>>> yea,  it kind of sucks,  but that is the reality
>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/ec61c953/attachment-0001.html 

From kurrent93 at gmail.com  Thu Jan 21 15:30:44 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 21:30:44 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>
	<CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>
Message-ID: <CAD44pJBwfm31UgrwbfrQK8tweWkXBAS259RR5VOnKejentUwhw@mail.gmail.com>

On Thu, Jan 21, 2016 at 9:03 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> both android and iOS have limitations on the message payload,  so the
> message is usually just a string.
>

Ok, so is there another convention for sending json data?

My use-case is, I want to send a notification to a specific user say "that
item you have been watching is now available" - and when the click on it,
the app opens, and they see a screen with price, currency, etc - a domain
model.

Is 'push' the right/normal way to do that? Or is there another convention?

Or would it be a combination of push, then do a rest request?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/72e1402f/attachment.html 

From lholmqui at redhat.com  Thu Jan 21 15:33:17 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Thu, 21 Jan 2016 15:33:17 -0500
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJBwfm31UgrwbfrQK8tweWkXBAS259RR5VOnKejentUwhw@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>
	<CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>
	<CAD44pJBwfm31UgrwbfrQK8tweWkXBAS259RR5VOnKejentUwhw@mail.gmail.com>
Message-ID: <CALD3Fd2yNpWG1-bsspD47xGLjTtkNJnWMRg7c14adKba_xeJMQ@mail.gmail.com>

On Thu, Jan 21, 2016 at 3:30 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Thu, Jan 21, 2016 at 9:03 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> both android and iOS have limitations on the message payload,  so the
>> message is usually just a string.
>>
>
> Ok, so is there another convention for sending json data?
>
> My use-case is, I want to send a notification to a specific user say "that
> item you have been watching is now available" - and when the click on it,
> the app opens, and they see a screen with price, currency, etc - a domain
> model.
>
> Is 'push' the right/normal way to do that? Or is there another convention?
>
> Or would it be a combination of push, then do a rest request?
>
i believe this is usually the practice,  you have the message plus some
meta-data in the payload.  then your app goes and fetches the info from a
REST endpoint or something.

>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/50ebbefd/attachment.html 

From kurrent93 at gmail.com  Thu Jan 21 16:03:27 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Thu, 21 Jan 2016 22:03:27 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
Message-ID: <CAD44pJD4ujkZiEWKnAXM10swbeVYHBSSQ5=Je7fA52hDS1DkRQ@mail.gmail.com>

On Thu, Jan 21, 2016 at 8:50 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> yea,  it kind of sucks,  but that is the reality
>
>>
Is it just with Cordova that push does not work in development?
I saw in this video - https://youtu.be/-hh-sEesocs - it works in ios.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160121/7fd740a6/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 02:29:41 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 08:29:41 +0100
Subject: [Aerogear-users] Testing push in Cordova
Message-ID: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>

Hello

I am trying to test the UPS and Cordova.

I have UPS setup, have setup a google account, have all the required pieces.

I have watched all the videos that demonstrate how it should work.

I am deploying the sample app via the android device emulator, and it does
get deployed.

However the UPS never sees any devices as connected, and no push messages
sent from UPS ever arrive.

What should I do to debug this? Are there any obvious things to look into?

Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/a2d2828b/attachment.html 

From edewit at redhat.com  Fri Jan 22 03:58:25 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 22 Jan 2016 09:58:25 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
Message-ID: <CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>

Hi Anton,

So if the device doesn't show up in the UPS console it will never receive a
message, so first thing to to check is if the register is performed in the
android log (adb logcat). If that is not the case there might be a
javascript problem, best way to determine that is by attaching a chrome
debugger (type "chrome://inspect" in a location bar). Check the console log
if there are any javascript or communication problems.

Hope this helps,


On Fri, Jan 22, 2016 at 8:29 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Hello
>
> I am trying to test the UPS and Cordova.
>
> I have UPS setup, have setup a google account, have all the required
> pieces.
>
> I have watched all the videos that demonstrate how it should work.
>
> I am deploying the sample app via the android device emulator, and it does
> get deployed.
>
> However the UPS never sees any devices as connected, and no push messages
> sent from UPS ever arrive.
>
> What should I do to debug this? Are there any obvious things to look into?
>
> Thanks
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/6a0587d3/attachment.html 

From edewit at redhat.com  Fri Jan 22 04:11:35 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 22 Jan 2016 10:11:35 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJBwfm31UgrwbfrQK8tweWkXBAS259RR5VOnKejentUwhw@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJChHHjiTtuh63PaZQ8C8Jnbu8jFHmX1SXfTxQAd075FsQ@mail.gmail.com>
	<CALD3Fd3xX_Gj_vctKhN7PPmPE+DN_WuikSsPxcGQ8B-7U4GqKA@mail.gmail.com>
	<CAD44pJBwfm31UgrwbfrQK8tweWkXBAS259RR5VOnKejentUwhw@mail.gmail.com>
Message-ID: <CAO2B-faSUDZ0+rPjDT5XmGVkpsx9=RSJ7aNVFRLxvzzeZBUuKQ@mail.gmail.com>

You can add meta data like that directly into the message [1] see
"user-data"


[1] https://aerogear.org/docs/unifiedpush/push-message-format-dev/

On Thu, Jan 21, 2016 at 9:30 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Thu, Jan 21, 2016 at 9:03 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> both android and iOS have limitations on the message payload,  so the
>> message is usually just a string.
>>
>
> Ok, so is there another convention for sending json data?
>
> My use-case is, I want to send a notification to a specific user say "that
> item you have been watching is now available" - and when the click on it,
> the app opens, and they see a screen with price, currency, etc - a domain
> model.
>
> Is 'push' the right/normal way to do that? Or is there another convention?
>
> Or would it be a combination of push, then do a rest request?
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/edfc1469/attachment-0001.html 

From edewit at redhat.com  Fri Jan 22 04:13:53 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 22 Jan 2016 10:13:53 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJD4ujkZiEWKnAXM10swbeVYHBSSQ5=Je7fA52hDS1DkRQ@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJD4ujkZiEWKnAXM10swbeVYHBSSQ5=Je7fA52hDS1DkRQ@mail.gmail.com>
Message-ID: <CAO2B-fY6zBKL_9w3QvP5-_sNpw_sDFgQLwdaWt-cPKvSSezVKQ@mail.gmail.com>

That video is using a real device as well, and a program to "project" the
screen of the device onto the desktop. If you don't have a device you could
use genymotion or the android emulator

On Thu, Jan 21, 2016 at 10:03 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Thu, Jan 21, 2016 at 8:50 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> yea,  it kind of sucks,  but that is the reality
>>
>>>
> Is it just with Cordova that push does not work in development?
> I saw in this video - https://youtu.be/-hh-sEesocs - it works in ios.
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/8d9df2be/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 05:12:42 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 11:12:42 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAO2B-fY6zBKL_9w3QvP5-_sNpw_sDFgQLwdaWt-cPKvSSezVKQ@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJD4ujkZiEWKnAXM10swbeVYHBSSQ5=Je7fA52hDS1DkRQ@mail.gmail.com>
	<CAO2B-fY6zBKL_9w3QvP5-_sNpw_sDFgQLwdaWt-cPKvSSezVKQ@mail.gmail.com>
Message-ID: <CAD44pJDxUD+0K_10TG3en4kjHHZbGTDHo5EJN+icvPHL4uPO5w@mail.gmail.com>

On Fri, Jan 22, 2016 at 10:13 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> If you don't have a device you could use genymotion or the android
> emulator


Ok, so to confirm, I should be able to send push, and have the device
registered in UPS, if I use the android emulator?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/ebcdb8c0/attachment.html 

From scm.blanc at gmail.com  Fri Jan 22 05:17:48 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Fri, 22 Jan 2016 11:17:48 +0100
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD44pJDxUD+0K_10TG3en4kjHHZbGTDHo5EJN+icvPHL4uPO5w@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJD4ujkZiEWKnAXM10swbeVYHBSSQ5=Je7fA52hDS1DkRQ@mail.gmail.com>
	<CAO2B-fY6zBKL_9w3QvP5-_sNpw_sDFgQLwdaWt-cPKvSSezVKQ@mail.gmail.com>
	<CAD44pJDxUD+0K_10TG3en4kjHHZbGTDHo5EJN+icvPHL4uPO5w@mail.gmail.com>
Message-ID: <CAD_dpu2_nEgz-k+UOXVJ+_a9_HtduRaz6b2-P4Ushe9f_zLFbA@mail.gmail.com>

Yes I was able to test push with the latest version of the emulator. But,
as Erik said, you could also try genymotion, it is pretty amazing stuff.

On Fri, Jan 22, 2016 at 11:12 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Fri, Jan 22, 2016 at 10:13 AM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> If you don't have a device you could use genymotion or the android
>> emulator
>
>
> Ok, so to confirm, I should be able to send push, and have the device
> registered in UPS, if I use the android emulator?
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/1347ede6/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 05:29:41 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 11:29:41 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
Message-ID: <CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>

Thanks Eric

Yes I did check in the chrome debugger, but there was no errors.

adb logcat - I am completely new to mobile development, so forgive me if my
questions are very newbie-ish.
I have found the following -
https://developer.android.com/tools/debugging/debugging-log.html - which
says:

> You can run LogCat through ADB or from DDMS, which allows you to read the
> messages in real time.

What is adb and DDMS? Are these in JBDS?
How do I write to the log? I can see some examples in the Aerogear samples,
that write to what looks like the javascript console. Do this get
transpiled to android java?


On Fri, Jan 22, 2016 at 9:58 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi Anton,
>
> So if the device doesn't show up in the UPS console it will never receive
> a message, so first thing to to check is if the register is performed in
> the android log (adb logcat). If that is not the case there might be a
> javascript problem, best way to determine that is by attaching a chrome
> debugger (type "chrome://inspect" in a location bar). Check the console log
> if there are any javascript or communication problems.
>
> Hope this helps,
>
>
> On Fri, Jan 22, 2016 at 8:29 AM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>> Hello
>>
>> I am trying to test the UPS and Cordova.
>>
>> I have UPS setup, have setup a google account, have all the required
>> pieces.
>>
>> I have watched all the videos that demonstrate how it should work.
>>
>> I am deploying the sample app via the android device emulator, and it
>> does get deployed.
>>
>> However the UPS never sees any devices as connected, and no push messages
>> sent from UPS ever arrive.
>>
>> What should I do to debug this? Are there any obvious things to look into?
>>
>> Thanks
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/3b6b5269/attachment.html 

From dpassos at redhat.com  Fri Jan 22 06:30:17 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 22 Jan 2016 09:30:17 -0200
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
Message-ID: <CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>

I really recommend you *don't* use Android emulator to play around
push/gcm.

On Fri, Jan 22, 2016 at 8:29 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Thanks Eric
>
> Yes I did check in the chrome debugger, but there was no errors.
>
> adb logcat - I am completely new to mobile development, so forgive me if
> my questions are very newbie-ish.
> I have found the following -
> https://developer.android.com/tools/debugging/debugging-log.html - which
> says:
>
>> You can run LogCat through ADB or from DDMS, which allows you to read the
>> messages in real time.
>
> What is adb and DDMS? Are these in JBDS?
> How do I write to the log? I can see some examples in the Aerogear
> samples, that write to what looks like the javascript console. Do this get
> transpiled to android java?
>
>
> On Fri, Jan 22, 2016 at 9:58 AM, Erik Jan de Wit <edewit at redhat.com>
> wrote:
>
>> Hi Anton,
>>
>> So if the device doesn't show up in the UPS console it will never receive
>> a message, so first thing to to check is if the register is performed in
>> the android log (adb logcat). If that is not the case there might be a
>> javascript problem, best way to determine that is by attaching a chrome
>> debugger (type "chrome://inspect" in a location bar). Check the console log
>> if there are any javascript or communication problems.
>>
>> Hope this helps,
>>
>>
>> On Fri, Jan 22, 2016 at 8:29 AM, Anton Hughes <kurrent93 at gmail.com>
>> wrote:
>>
>>> Hello
>>>
>>> I am trying to test the UPS and Cordova.
>>>
>>> I have UPS setup, have setup a google account, have all the required
>>> pieces.
>>>
>>> I have watched all the videos that demonstrate how it should work.
>>>
>>> I am deploying the sample app via the android device emulator, and it
>>> does get deployed.
>>>
>>> However the UPS never sees any devices as connected, and no push
>>> messages sent from UPS ever arrive.
>>>
>>> What should I do to debug this? Are there any obvious things to look
>>> into?
>>>
>>> Thanks
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>
>>
>> --
>> Cheers,
>>        Erik Jan
>>
>> _______________________________________________
>> 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
>
>


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/ec25b6e3/attachment-0001.html 

From dpassos at redhat.com  Fri Jan 22 06:31:37 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 22 Jan 2016 09:31:37 -0200
Subject: [Aerogear-users] Qustions about Push and Cordova
In-Reply-To: <CAD_dpu2_nEgz-k+UOXVJ+_a9_HtduRaz6b2-P4Ushe9f_zLFbA@mail.gmail.com>
References: <CAD44pJB2e5OG9d0e5eBV3B7BVY+La79PtaoCg+tqiFGQV_nSxA@mail.gmail.com>
	<CALD3Fd2PEn0Zn2vyAZQvaaf3t7F5JCSRk_r3w1=Gyk=B1PXSGQ@mail.gmail.com>
	<CAD44pJA_4jf8xWK8E0WSizx2JuhTMzwrB3ET_oUtya-Em4b_-Q@mail.gmail.com>
	<CALD3Fd3vZttk3Ero9Rz6ZZh=h6m=VFv3T+YCKUJ-mJ87Rk6Ddw@mail.gmail.com>
	<CAD44pJAnwE0T0JPQgJLewdzPHA0kmU910z2SF4Fqio5pf7SaLA@mail.gmail.com>
	<CALD3Fd1mjvEw4_HWS-8zkxL6hmSYkswdBEwAyzx_RW5PJ7mfKg@mail.gmail.com>
	<CAD44pJBQ8BUaUg_BOT6Yx2GpDPFGB6OAGqed-Uxt9MQ_n9sKig@mail.gmail.com>
	<CALD3Fd2gednPvnJ4pZkbfCsRLGEbe-t_j=zXsTy_4yHhmM6D7w@mail.gmail.com>
	<CAD44pJD4ujkZiEWKnAXM10swbeVYHBSSQ5=Je7fA52hDS1DkRQ@mail.gmail.com>
	<CAO2B-fY6zBKL_9w3QvP5-_sNpw_sDFgQLwdaWt-cPKvSSezVKQ@mail.gmail.com>
	<CAD44pJDxUD+0K_10TG3en4kjHHZbGTDHo5EJN+icvPHL4uPO5w@mail.gmail.com>
	<CAD_dpu2_nEgz-k+UOXVJ+_a9_HtduRaz6b2-P4Ushe9f_zLFbA@mail.gmail.com>
Message-ID: <CADF=h2uk+Ua4RDqAJ8Qma0ZW956+XnH-cF9R8GxXb8Ce=BgbcQ@mail.gmail.com>

Just to be clear Genymotion *don't* support GCM/Push notification by
default.

On Fri, Jan 22, 2016 at 8:17 AM, Sebastien Blanc <scm.blanc at gmail.com>
wrote:

> Yes I was able to test push with the latest version of the emulator. But,
> as Erik said, you could also try genymotion, it is pretty amazing stuff.
>
> On Fri, Jan 22, 2016 at 11:12 AM, Anton Hughes <kurrent93 at gmail.com>
> wrote:
>
>>
>> On Fri, Jan 22, 2016 at 10:13 AM, Erik Jan de Wit <edewit at redhat.com>
>> wrote:
>>
>>> If you don't have a device you could use genymotion or the android
>>> emulator
>>
>>
>> Ok, so to confirm, I should be able to send push, and have the device
>> registered in UPS, if I use the android emulator?
>>
>> _______________________________________________
>> 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
>
>


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/4e5acc3b/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 06:34:09 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 12:34:09 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
Message-ID: <CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>

On Fri, Jan 22, 2016 at 12:30 PM, Daniel Passos <dpassos at redhat.com> wrote:

> I really recommend you *don't* use Android emulator to play around
> push/gcm.
>

HI Daniel - I appreciate the feedback. I need all the help I can get right
now as I am very green.
However, I have been told that push does not work when using the cordova
'emulator' (not sure if that is the right word).

For now, I just need to see that UPS and cordova works - that I can push a
message. That is the stage I am at.

What are your reasons for advocating for not using Android emulator?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/1700c911/attachment.html 

From dpassos at redhat.com  Fri Jan 22 06:42:15 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Fri, 22 Jan 2016 09:42:15 -0200
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
Message-ID: <CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>

On Fri, Jan 22, 2016 at 9:34 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Fri, Jan 22, 2016 at 12:30 PM, Daniel Passos <dpassos at redhat.com>
> wrote:
>
>> I really recommend you *don't* use Android emulator to play around
>> push/gcm.
>>
>
> HI Daniel - I appreciate the feedback. I need all the help I can get right
> now as I am very green.
> However, I have been told that push does not work when using the cordova
> 'emulator' (not sure if that is the right word).
>
> For now, I just need to see that UPS and cordova works - that I can push a
> message. That is the stage I am at.
>
> What are your reasons for advocating for not using Android emulator?
>

By default GCM/Push don't work on Google emulator, only in the last
versions, but I always prefer test it in a real device to prevent problems.

Another tip you need to have and Gmail/Google valid account on the device.

Emulator and don't have a Google account on device made me too much
problems in the past

_______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/e8428e7d/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 06:47:33 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 12:47:33 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
Message-ID: <CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>

On Fri, Jan 22, 2016 at 12:42 PM, Daniel Passos <dpassos at redhat.com> wrote:

> By default GCM/Push don't work on Google emulator, only in the last
> versions, but I always prefer test it in a real device to prevent problems.


If I have to deploy to a real device to do basic testing I will go (more)
insane.
There has to be away of testing push that doesnt involve deploying to an
actual device.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/292244c0/attachment.html 

From rob.aerogear at robertwillett.com  Fri Jan 22 06:59:37 2016
From: rob.aerogear at robertwillett.com (Rob Willett)
Date: Fri, 22 Jan 2016 11:59:37 +0000
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
	<CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
Message-ID: <E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>

Just to throw my 2c in here.

We test push notifications on the Genymotion emulator. Out of the box 
Genymotion does NOT support notifications but its pretty easy to get 
notifications working on Genymotion.

We used this page

http://inthecheesefactory.com/blog/how-to-install-google-services-on-genymotion/en

to get it working. This works with all the commercial push providers we 
have checked out.

We have not found a way to get Android 6 working with push on Genymotion 
but since Android 6 is still preview on Genymotion its not an issue for 
us.

However we haven?t found that deploying to a real device (Nexus 5) to 
be much slower than Genymotion. We?re happy to deploy to any as its 
pretty speedy either way.

Unclear as to why deploying to a real device is such a problem, we 
develop on iPhone and Android using Cordova and even though I like the 
iPhone, the development and debugging tools on a real Android device are 
excellent and fast. When we have a real problem, we tend to ignore Xcode 
and Safari and the iPhone and debug it on a real Android device. We 
don?t have any real issues, though we always want things to be 
quicker.

Rob

On 22 Jan 2016, at 11:47, Anton Hughes wrote:

> On Fri, Jan 22, 2016 at 12:42 PM, Daniel Passos <dpassos at redhat.com> 
> wrote:
>
>> By default GCM/Push don't work on Google emulator, only in the last
>> versions, but I always prefer test it in a real device to prevent 
>> problems.
>
>
> If I have to deploy to a real device to do basic testing I will go 
> (more)
> insane.
> There has to be away of testing push that doesnt involve deploying to 
> an
> actual device.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users


From kurrent93 at gmail.com  Fri Jan 22 07:10:23 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 13:10:23 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
	<CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
	<E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>
Message-ID: <CAD44pJBPrxQzxhnW2HFOcrcccZg8O7iy8hUH50xD7=s=SPDKsA@mail.gmail.com>

Thanks Rob
On Fri, Jan 22, 2016 at 12:59 PM, Rob Willett <
rob.aerogear at robertwillett.com> wrote:

> Unclear as to why deploying to a real device is such a problem, we
> develop on iPhone and Android using Cordova and even though I like the
> iPhone, the development and debugging tools on a real Android device are
> excellent and fast. When we have a real problem, we tend to ignore Xcode
> and Safari and the iPhone and debug it on a real Android device. We
> don?t have any real issues, though we always want things to be
> quicker.
>

Its a problem for me as I dont have a cell phone - seriously.
But, it just sounds odd, to have to deploy and install on a new piece of
hardware each time you want to test. My usual workflow would be to develop
locally, then when things are working, then deploy.

And, for now, I am just doing a proof of concept - my goal is just to prove
that it is possible to send a push notification from UPS to android using
cordova. I'm surprised at how complicated it is. But I suppose my confusion
and frustration is simply because I am new to this style of developing.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/92cbe7b9/attachment-0001.html 

From rob.aerogear at robertwillett.com  Fri Jan 22 07:22:57 2016
From: rob.aerogear at robertwillett.com (Rob Willett)
Date: Fri, 22 Jan 2016 12:22:57 +0000
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJBPrxQzxhnW2HFOcrcccZg8O7iy8hUH50xD7=s=SPDKsA@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
	<CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
	<E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>
	<CAD44pJBPrxQzxhnW2HFOcrcccZg8O7iy8hUH50xD7=s=SPDKsA@mail.gmail.com>
Message-ID: <2912A87D-0002-4870-991C-7F3DBA472076@robertwillett.com>

Anton,

Its difficult to do some things without a phone, you can certainly 
develop on Cordova and get a long way on screens designs, controllers, 
services, posting to and getting stuff from servers but somethings need 
a hardware device.

Off the top of my head things that don?t work properly on 
iPhone/Android simulators or at all.

1. Background processing. JavaScript timers continue to work in the 
background but do not on a real phone. Sounds innocuous but its a 
massive hassle for us.
2. GPS is very limited on the iPhone emulator. You can set simple GPS 
routes up and thats it. The genymotion has a GPS on off switch to save a 
position, useful for very, very limited uses.
3. No notifications on the iPhone emulator. Zilch. You can get them on 
the Genymotion with the link I posted.
4. No In-App purchasing on the iPhone. No access to the sandbox, its a 
nightmare even on a real phone. No idea on Android as we have up on the 
iPhone.
5. Some weird effects of different versions of IOS and background 
processing with geolocation and posting to servers with ATS. We can?t 
work it out at all, so we use real phones.

You can get so far without a phone but at the end of the day you will 
need one to develop and test. There is no getting away from it. Ups 
cannot develop and simply deploy and hope it all works. Emulators will 
work, but not with any success for at least the things I?ve quoted 
above.

Rob

On 22 Jan 2016, at 12:10, Anton Hughes wrote:

> Thanks Rob
> On Fri, Jan 22, 2016 at 12:59 PM, Rob Willett <
> rob.aerogear at robertwillett.com> wrote:
>
>> Unclear as to why deploying to a real device is such a problem, we
>> develop on iPhone and Android using Cordova and even though I like 
>> the
>> iPhone, the development and debugging tools on a real Android device 
>> are
>> excellent and fast. When we have a real problem, we tend to ignore 
>> Xcode
>> and Safari and the iPhone and debug it on a real Android device. We
>> don?t have any real issues, though we always want things to be
>> quicker.
>>
>
> Its a problem for me as I dont have a cell phone - seriously.
> But, it just sounds odd, to have to deploy and install on a new piece 
> of
> hardware each time you want to test. My usual workflow would be to 
> develop
> locally, then when things are working, then deploy.
>
> And, for now, I am just doing a proof of concept - my goal is just to 
> prove
> that it is possible to send a push notification from UPS to android 
> using
> cordova. I'm surprised at how complicated it is. But I suppose my 
> confusion
> and frustration is simply because I am new to this style of 
> developing.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users

From kurrent93 at gmail.com  Fri Jan 22 07:51:40 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 13:51:40 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <2912A87D-0002-4870-991C-7F3DBA472076@robertwillett.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
	<CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
	<E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>
	<CAD44pJBPrxQzxhnW2HFOcrcccZg8O7iy8hUH50xD7=s=SPDKsA@mail.gmail.com>
	<2912A87D-0002-4870-991C-7F3DBA472076@robertwillett.com>
Message-ID: <CAD44pJAADk63AJxnkKiMCztAhWPD57bYHDkFhJmZ+_BHyU3k3Q@mail.gmail.com>

Thanks Rob - really appreciate this.

May I recommend that this is published on the aerogear website. This kind
of knowledge is gained through hard knocks. It can save many others the
same pain.

On Fri, Jan 22, 2016 at 1:22 PM, Rob Willett <rob.aerogear at robertwillett.com
> wrote:

> Anton,
>
> Its difficult to do some things without a phone, you can certainly
> develop on Cordova and get a long way on screens designs, controllers,
> services, posting to and getting stuff from servers but somethings need
> a hardware device.
>
> Off the top of my head things that don?t work properly on
> iPhone/Android simulators or at all.
>
> 1. Background processing. JavaScript timers continue to work in the
> background but do not on a real phone. Sounds innocuous but its a
> massive hassle for us.
> 2. GPS is very limited on the iPhone emulator. You can set simple GPS
> routes up and thats it. The genymotion has a GPS on off switch to save a
> position, useful for very, very limited uses.
> 3. No notifications on the iPhone emulator. Zilch. You can get them on
> the Genymotion with the link I posted.
> 4. No In-App purchasing on the iPhone. No access to the sandbox, its a
> nightmare even on a real phone. No idea on Android as we have up on the
> iPhone.
> 5. Some weird effects of different versions of IOS and background
> processing with geolocation and posting to servers with ATS. We can?t
> work it out at all, so we use real phones.
>
> You can get so far without a phone but at the end of the day you will
> need one to develop and test. There is no getting away from it. Ups
> cannot develop and simply deploy and hope it all works. Emulators will
> work, but not with any success for at least the things I?ve quoted
> above.
>
> Rob
>
> On 22 Jan 2016, at 12:10, Anton Hughes wrote:
>
> > Thanks Rob
> > On Fri, Jan 22, 2016 at 12:59 PM, Rob Willett <
> > rob.aerogear at robertwillett.com> wrote:
> >
> >> Unclear as to why deploying to a real device is such a problem, we
> >> develop on iPhone and Android using Cordova and even though I like
> >> the
> >> iPhone, the development and debugging tools on a real Android device
> >> are
> >> excellent and fast. When we have a real problem, we tend to ignore
> >> Xcode
> >> and Safari and the iPhone and debug it on a real Android device. We
> >> don?t have any real issues, though we always want things to be
> >> quicker.
> >>
> >
> > Its a problem for me as I dont have a cell phone - seriously.
> > But, it just sounds odd, to have to deploy and install on a new piece
> > of
> > hardware each time you want to test. My usual workflow would be to
> > develop
> > locally, then when things are working, then deploy.
> >
> > And, for now, I am just doing a proof of concept - my goal is just to
> > prove
> > that it is possible to send a push notification from UPS to android
> > using
> > cordova. I'm surprised at how complicated it is. But I suppose my
> > confusion
> > and frustration is simply because I am new to this style of
> > developing.
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/8f19ca56/attachment.html 

From rob.aerogear at robertwillett.com  Fri Jan 22 07:54:25 2016
From: rob.aerogear at robertwillett.com (Rob Willett)
Date: Fri, 22 Jan 2016 12:54:25 +0000
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJAADk63AJxnkKiMCztAhWPD57bYHDkFhJmZ+_BHyU3k3Q@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
	<CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
	<E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>
	<CAD44pJBPrxQzxhnW2HFOcrcccZg8O7iy8hUH50xD7=s=SPDKsA@mail.gmail.com>
	<2912A87D-0002-4870-991C-7F3DBA472076@robertwillett.com>
	<CAD44pJAADk63AJxnkKiMCztAhWPD57bYHDkFhJmZ+_BHyU3k3Q@mail.gmail.com>
Message-ID: <E83172C7-DFB0-4291-B028-194271A60A41@robertwillett.com>

They are welcome to use it as they see fit, though the only things that 
should be there is the push notification stuff, the rest is my problem 
:)

On 22 Jan 2016, at 12:51, Anton Hughes wrote:

> Thanks Rob - really appreciate this.
>
> May I recommend that this is published on the aerogear website. This 
> kind
> of knowledge is gained through hard knocks. It can save many others 
> the
> same pain.
>
> On Fri, Jan 22, 2016 at 1:22 PM, Rob Willett 
> <rob.aerogear at robertwillett.com
>> wrote:
>
>> Anton,
>>
>> Its difficult to do some things without a phone, you can certainly
>> develop on Cordova and get a long way on screens designs, 
>> controllers,
>> services, posting to and getting stuff from servers but somethings 
>> need
>> a hardware device.
>>
>> Off the top of my head things that don?t work properly on
>> iPhone/Android simulators or at all.
>>
>> 1. Background processing. JavaScript timers continue to work in the
>> background but do not on a real phone. Sounds innocuous but its a
>> massive hassle for us.
>> 2. GPS is very limited on the iPhone emulator. You can set simple GPS
>> routes up and thats it. The genymotion has a GPS on off switch to 
>> save a
>> position, useful for very, very limited uses.
>> 3. No notifications on the iPhone emulator. Zilch. You can get them 
>> on
>> the Genymotion with the link I posted.
>> 4. No In-App purchasing on the iPhone. No access to the sandbox, its 
>> a
>> nightmare even on a real phone. No idea on Android as we have up on 
>> the
>> iPhone.
>> 5. Some weird effects of different versions of IOS and background
>> processing with geolocation and posting to servers with ATS. We 
>> can?t
>> work it out at all, so we use real phones.
>>
>> You can get so far without a phone but at the end of the day you will
>> need one to develop and test. There is no getting away from it. Ups
>> cannot develop and simply deploy and hope it all works. Emulators 
>> will
>> work, but not with any success for at least the things I?ve quoted
>> above.
>>
>> Rob
>>
>> On 22 Jan 2016, at 12:10, Anton Hughes wrote:
>>
>>> Thanks Rob
>>> On Fri, Jan 22, 2016 at 12:59 PM, Rob Willett <
>>> rob.aerogear at robertwillett.com> wrote:
>>>
>>>> Unclear as to why deploying to a real device is such a problem, we
>>>> develop on iPhone and Android using Cordova and even though I like
>>>> the
>>>> iPhone, the development and debugging tools on a real Android 
>>>> device
>>>> are
>>>> excellent and fast. When we have a real problem, we tend to ignore
>>>> Xcode
>>>> and Safari and the iPhone and debug it on a real Android device. We
>>>> don?t have any real issues, though we always want things to be
>>>> quicker.
>>>>
>>>
>>> Its a problem for me as I dont have a cell phone - seriously.
>>> But, it just sounds odd, to have to deploy and install on a new 
>>> piece
>>> of
>>> hardware each time you want to test. My usual workflow would be to
>>> develop
>>> locally, then when things are working, then deploy.
>>>
>>> And, for now, I am just doing a proof of concept - my goal is just 
>>> to
>>> prove
>>> that it is possible to send a push notification from UPS to android
>>> using
>>> cordova. I'm surprised at how complicated it is. But I suppose my
>>> confusion
>>> and frustration is simply because I am new to this style of
>>> developing.
>>> _______________________________________________
>>> 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
>>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users

From kurrent93 at gmail.com  Fri Jan 22 08:11:34 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 14:11:34 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <E83172C7-DFB0-4291-B028-194271A60A41@robertwillett.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CAO2B-fZvEUy5_K_oVeO=GEVXcbB9_+vY0FVxuHGSq0780S4ajg@mail.gmail.com>
	<CAD44pJDm1rRcRa6qBQs_xxASrRS-spjFc8JgNPJ0DR-xxyFTDQ@mail.gmail.com>
	<CADF=h2vTiiJCredMFwy_mkGMNMV7MkSn76kPQU38+ccO=wp3UA@mail.gmail.com>
	<CAD44pJC=ZaR3hfUVvU=ig0V3cc3pydgKkiwCBddi+aeH_z5Hug@mail.gmail.com>
	<CADF=h2tYOsUbiFPH7SKmJXO_ngiSLFy95hv8QyYJdwr2d3UA4Q@mail.gmail.com>
	<CAD44pJDiUpR0NWSOpj47Y9=37SNWVoUiyQnaRY6-uGKH+wDuBw@mail.gmail.com>
	<E82F16FF-76F3-4D6E-9B18-881CD2A26ECD@robertwillett.com>
	<CAD44pJBPrxQzxhnW2HFOcrcccZg8O7iy8hUH50xD7=s=SPDKsA@mail.gmail.com>
	<2912A87D-0002-4870-991C-7F3DBA472076@robertwillett.com>
	<CAD44pJAADk63AJxnkKiMCztAhWPD57bYHDkFhJmZ+_BHyU3k3Q@mail.gmail.com>
	<E83172C7-DFB0-4291-B028-194271A60A41@robertwillett.com>
Message-ID: <CAD44pJAfndUawfAmfa4GwfUExG+5FMjUnH7AJu24TR+wNZocBQ@mail.gmail.com>

So, to be clear, if I do the steps on
http://inthecheesefactory.com/blog/how-to-install-google-services-on-genymotion/en
then I should be able to test push without having to find borrow my
girlfriends phone?

Is there any free alternatives to genymotion that work with push (even if
some hacks are required)?

As mentioned previously, at this stage it is just a PoC - so would like to
avoid having to buy any hardware or software, if possible.


On Fri, Jan 22, 2016 at 1:54 PM, Rob Willett <rob.aerogear at robertwillett.com
> wrote:

> They are welcome to use it as they see fit, though the only things that
> should be there is the push notification stuff, the rest is my problem
> :)
>
> On 22 Jan 2016, at 12:51, Anton Hughes wrote:
>
> > Thanks Rob - really appreciate this.
> >
> > May I recommend that this is published on the aerogear website. This
> > kind
> > of knowledge is gained through hard knocks. It can save many others
> > the
> > same pain.
> >
> > On Fri, Jan 22, 2016 at 1:22 PM, Rob Willett
> > <rob.aerogear at robertwillett.com
> >> wrote:
> >
> >> Anton,
> >>
> >> Its difficult to do some things without a phone, you can certainly
> >> develop on Cordova and get a long way on screens designs,
> >> controllers,
> >> services, posting to and getting stuff from servers but somethings
> >> need
> >> a hardware device.
> >>
> >> Off the top of my head things that don?t work properly on
> >> iPhone/Android simulators or at all.
> >>
> >> 1. Background processing. JavaScript timers continue to work in the
> >> background but do not on a real phone. Sounds innocuous but its a
> >> massive hassle for us.
> >> 2. GPS is very limited on the iPhone emulator. You can set simple GPS
> >> routes up and thats it. The genymotion has a GPS on off switch to
> >> save a
> >> position, useful for very, very limited uses.
> >> 3. No notifications on the iPhone emulator. Zilch. You can get them
> >> on
> >> the Genymotion with the link I posted.
> >> 4. No In-App purchasing on the iPhone. No access to the sandbox, its
> >> a
> >> nightmare even on a real phone. No idea on Android as we have up on
> >> the
> >> iPhone.
> >> 5. Some weird effects of different versions of IOS and background
> >> processing with geolocation and posting to servers with ATS. We
> >> can?t
> >> work it out at all, so we use real phones.
> >>
> >> You can get so far without a phone but at the end of the day you will
> >> need one to develop and test. There is no getting away from it. Ups
> >> cannot develop and simply deploy and hope it all works. Emulators
> >> will
> >> work, but not with any success for at least the things I?ve quoted
> >> above.
> >>
> >> Rob
> >>
> >> On 22 Jan 2016, at 12:10, Anton Hughes wrote:
> >>
> >>> Thanks Rob
> >>> On Fri, Jan 22, 2016 at 12:59 PM, Rob Willett <
> >>> rob.aerogear at robertwillett.com> wrote:
> >>>
> >>>> Unclear as to why deploying to a real device is such a problem, we
> >>>> develop on iPhone and Android using Cordova and even though I like
> >>>> the
> >>>> iPhone, the development and debugging tools on a real Android
> >>>> device
> >>>> are
> >>>> excellent and fast. When we have a real problem, we tend to ignore
> >>>> Xcode
> >>>> and Safari and the iPhone and debug it on a real Android device. We
> >>>> don?t have any real issues, though we always want things to be
> >>>> quicker.
> >>>>
> >>>
> >>> Its a problem for me as I dont have a cell phone - seriously.
> >>> But, it just sounds odd, to have to deploy and install on a new
> >>> piece
> >>> of
> >>> hardware each time you want to test. My usual workflow would be to
> >>> develop
> >>> locally, then when things are working, then deploy.
> >>>
> >>> And, for now, I am just doing a proof of concept - my goal is just
> >>> to
> >>> prove
> >>> that it is possible to send a push notification from UPS to android
> >>> using
> >>> cordova. I'm surprised at how complicated it is. But I suppose my
> >>> confusion
> >>> and frustration is simply because I am new to this style of
> >>> developing.
> >>> _______________________________________________
> >>> 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
> >>
> > _______________________________________________
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/d7b36c2b/attachment-0001.html 

From lholmqui at redhat.com  Fri Jan 22 08:25:12 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 22 Jan 2016 08:25:12 -0500
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
Message-ID: <CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>

On Fri, Jan 22, 2016 at 2:29 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Hello
>
> I am trying to test the UPS and Cordova.
>
> I have UPS setup, have setup a google account, have all the required
> pieces.
>
> I have watched all the videos that demonstrate how it should work.
>
> I am deploying the sample app via the android device emulator, and it does
> get deployed.
>
> However the UPS never sees any devices as connected, and no push messages
> sent from UPS ever arrive.
>
just a thought that popped into my head.   The url pointing to your UPS
server shouldn't be localhost, since there is no localhost on the device.
 not sure if thats how you have it configured, though. but this always
bites me

>
> What should I do to debug this? Are there any obvious things to look into?
>
> Thanks
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/4fee439f/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 08:28:15 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 14:28:15 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
Message-ID: <CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>

On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

> just a thought that popped into my head.   The url pointing to your UPS
> server shouldn't be localhost, since there is no localhost on the device.
>  not sure if thats how you have it configured, though. but this always
> bites me


The wise expression of Homer Simpson comes rushing into mind!
I'm away from my dev environment, so cannot test - but, yes I am using
localhost in the cordova project.

So if not localhost, then what?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/7f603b7f/attachment.html 

From lholmqui at redhat.com  Fri Jan 22 08:31:07 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 22 Jan 2016 08:31:07 -0500
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
	<CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
Message-ID: <CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>

On Fri, Jan 22, 2016 at 8:28 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

>
> On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>> just a thought that popped into my head.   The url pointing to your UPS
>> server shouldn't be localhost, since there is no localhost on the device.
>>  not sure if thats how you have it configured, though. but this always
>> bites me
>
>
> The wise expression of Homer Simpson comes rushing into mind!
> I'm away from my dev environment, so cannot test - but, yes I am using
> localhost in the cordova project.
>
> So if not localhost, then what?
>
if you are running the UPS server on your local machine, then it would be
your IP instead of localhost.  The device just needs to "see" it, so that
means you need to be on the same network.   unless you are running it in
the cloud or something

>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/abfc3d4a/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 08:35:48 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Fri, 22 Jan 2016 14:35:48 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
	<CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
	<CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>
Message-ID: <CAD44pJC3BmrmUUCGyNEata+aRhUm32WxhtWgdkec0Q9WphcxbA@mail.gmail.com>

Thanks Luke. I will try this.

On Fri, Jan 22, 2016 at 2:31 PM, Luke Holmquist <lholmqui at redhat.com> wrote:

>
>
> On Fri, Jan 22, 2016 at 8:28 AM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>>
>> On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>> just a thought that popped into my head.   The url pointing to your UPS
>>> server shouldn't be localhost, since there is no localhost on the device.
>>>  not sure if thats how you have it configured, though. but this always
>>> bites me
>>
>>
>> The wise expression of Homer Simpson comes rushing into mind!
>> I'm away from my dev environment, so cannot test - but, yes I am using
>> localhost in the cordova project.
>>
>> So if not localhost, then what?
>>
> if you are running the UPS server on your local machine, then it would be
> your IP instead of localhost.  The device just needs to "see" it, so that
> means you need to be on the same network.   unless you are running it in
> the cloud or something
>
>>
>> _______________________________________________
>> 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
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160122/123c747e/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 18:21:49 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Sat, 23 Jan 2016 00:21:49 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJC3BmrmUUCGyNEata+aRhUm32WxhtWgdkec0Q9WphcxbA@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
	<CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
	<CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>
	<CAD44pJC3BmrmUUCGyNEata+aRhUm32WxhtWgdkec0Q9WphcxbA@mail.gmail.com>
Message-ID: <CAD44pJBx6wiLjytDiqDWM6Oq=tgzjNpaixXO0DFviVF0c1godA@mail.gmail.com>

Ok, I have managed to get setup with Genymotion, and have the google tools
installed.

How, then, can I deploy the cordova project to the genymotion vm? Is there
a way to do that from within Eclipse?

Thanks

On Fri, Jan 22, 2016 at 2:35 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Thanks Luke. I will try this.
>
> On Fri, Jan 22, 2016 at 2:31 PM, Luke Holmquist <lholmqui at redhat.com>
> wrote:
>
>>
>>
>> On Fri, Jan 22, 2016 at 8:28 AM, Anton Hughes <kurrent93 at gmail.com>
>> wrote:
>>
>>>
>>> On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>> just a thought that popped into my head.   The url pointing to your UPS
>>>> server shouldn't be localhost, since there is no localhost on the device.
>>>>  not sure if thats how you have it configured, though. but this always
>>>> bites me
>>>
>>>
>>> The wise expression of Homer Simpson comes rushing into mind!
>>> I'm away from my dev environment, so cannot test - but, yes I am using
>>> localhost in the cordova project.
>>>
>>> So if not localhost, then what?
>>>
>> if you are running the UPS server on your local machine, then it would be
>> your IP instead of localhost.  The device just needs to "see" it, so that
>> means you need to be on the same network.   unless you are running it in
>> the cloud or something
>>
>>>
>>> _______________________________________________
>>> 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
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/4e2bd0cd/attachment-0001.html 

From kurrent93 at gmail.com  Fri Jan 22 18:51:13 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Sat, 23 Jan 2016 00:51:13 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJBx6wiLjytDiqDWM6Oq=tgzjNpaixXO0DFviVF0c1godA@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
	<CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
	<CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>
	<CAD44pJC3BmrmUUCGyNEata+aRhUm32WxhtWgdkec0Q9WphcxbA@mail.gmail.com>
	<CAD44pJBx6wiLjytDiqDWM6Oq=tgzjNpaixXO0DFviVF0c1godA@mail.gmail.com>
Message-ID: <CAD44pJDwLDSccxf9paL7KLLhKsgD+EHCMT1nVGHWODQ-cOREDg@mail.gmail.com>

Ok so I managed to deploy my cordova app onto genymotion. Actually that
wasnt too difficult.
But, alas, it still does not connect to the UPS.

I have updated the pushServerURL value to use my hosts ip.

My index.html looks like this - I notice it is referencing cordova.js, but
this file is missing in the eclipse project. I assume eclipse automagically
adds it when the project is built.
Ive removed the send, variant and variant secret - to protect the identity
of the innocent.

<!DOCTYPE HTML>
<html>
<head>
  <title>Demo</title>
</head>
<body>

<script type="text/javascript" charset="utf-8" src="cordova.js"></script>
<script type="text/javascript" charset="utf-8"
src="jquery_1.5.2.min.js"></script>

<script type="text/javascript">

var app = {
 // Application Constructor
 initialize: function() {
   this.bindEvents();
 },
 // Bind Event Listeners
 //
 // Bind any events that are required on startup. Common events are:
 // 'load', 'deviceready', 'offline', and 'online'.
 bindEvents: function() {
   document.addEventListener('deviceready', this.onDeviceReady, false);
 },
 // deviceready Event Handler
 //
 // The scope of 'this' is the event. In order to call the 'receivedEvent'
 // function, we must explicitly call 'app.receivedEvent(...);'
 onDeviceReady: function() {
   app.receivedEvent('deviceready');
   var pushConfig = {
     pushServerURL: "http://192.168.1.40:8080/ag-push/",
     android: {
       senderID: "",
       variantID: "",
       variantSecret: ""
     }
   };
push.register(app.onNotification, successHandler, errorHandler, pushConfig);

function successHandler() {
 console.log('success')
}

function errorHandler(message) {
 console.log('error ' + message);
}
},
onNotification: function(event) {
 alert(event.alert);
},
// Update DOM on a Received Event
receivedEvent: function(id) {
 var parentElement = document.getElementById(id);
 var listeningElement = parentElement.querySelector('.listening');
 var receivedElement = parentElement.querySelector('.received');

 listeningElement.setAttribute('style', 'display:none;');
 receivedElement.setAttribute('style', 'display:block;');

 console.log('Received Event: ' + id);
}
};

app.initialize();

  document.addEventListener('deviceready', onDeviceReady, true);

</script>
<div id="home">
  <div id="app-status-div">
    <ul id="app-status-ul">
      <li>AeroGear PushPlugin Unified Push Demo</li>
    </ul>
  </div>
</div>
</body>
</html>

Can anyone see anything obviously wrong?

How does one debug in such a situation?

Thanks


On Sat, Jan 23, 2016 at 12:21 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Ok, I have managed to get setup with Genymotion, and have the google tools
> installed.
>
> How, then, can I deploy the cordova project to the genymotion vm? Is there
> a way to do that from within Eclipse?
>
> Thanks
>
> On Fri, Jan 22, 2016 at 2:35 PM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>> Thanks Luke. I will try this.
>>
>> On Fri, Jan 22, 2016 at 2:31 PM, Luke Holmquist <lholmqui at redhat.com>
>> wrote:
>>
>>>
>>>
>>> On Fri, Jan 22, 2016 at 8:28 AM, Anton Hughes <kurrent93 at gmail.com>
>>> wrote:
>>>
>>>>
>>>> On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>> just a thought that popped into my head.   The url pointing to your
>>>>> UPS server shouldn't be localhost, since there is no localhost on the
>>>>> device.  not sure if thats how you have it configured, though. but this
>>>>> always bites me
>>>>
>>>>
>>>> The wise expression of Homer Simpson comes rushing into mind!
>>>> I'm away from my dev environment, so cannot test - but, yes I am using
>>>> localhost in the cordova project.
>>>>
>>>> So if not localhost, then what?
>>>>
>>> if you are running the UPS server on your local machine, then it would
>>> be your IP instead of localhost.  The device just needs to "see" it, so
>>> that means you need to be on the same network.   unless you are running it
>>> in the cloud or something
>>>
>>>>
>>>> _______________________________________________
>>>> 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
>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/f76a570a/attachment.html 

From kurrent93 at gmail.com  Fri Jan 22 19:51:07 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Sat, 23 Jan 2016 01:51:07 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJDwLDSccxf9paL7KLLhKsgD+EHCMT1nVGHWODQ-cOREDg@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
	<CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
	<CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>
	<CAD44pJC3BmrmUUCGyNEata+aRhUm32WxhtWgdkec0Q9WphcxbA@mail.gmail.com>
	<CAD44pJBx6wiLjytDiqDWM6Oq=tgzjNpaixXO0DFviVF0c1godA@mail.gmail.com>
	<CAD44pJDwLDSccxf9paL7KLLhKsgD+EHCMT1nVGHWODQ-cOREDg@mail.gmail.com>
Message-ID: <CAD44pJD+iCU1FHn7HZWgzZ=4dqJNr48k1ayFE2GRAZrrO_GZug@mail.gmail.com>

Ok, I found the problem (see below) - but not the solution.

file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear.ajax.js
Failed to load resource: net::ERR_FILE_NOT_FOUND
file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear-push.js
Failed to load resource: net::ERR_FILE_NOT_FOUND
cordova.js:1418 Uncaught Error: Module aerogear-cordova-push.AeroGear.ajax
does not exist.
cordova.js:1183 deviceready has not fired after 5 seconds.
cordova.js:1176 Channel not fired: onPluginsReady
cordova.js:1176 Channel not fired: onCordovaReady

The resources that failed to load are present in the project.
[image: Inline image 1]

On Sat, Jan 23, 2016 at 12:51 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Ok so I managed to deploy my cordova app onto genymotion. Actually that
> wasnt too difficult.
> But, alas, it still does not connect to the UPS.
>
> I have updated the pushServerURL value to use my hosts ip.
>
> My index.html looks like this - I notice it is referencing cordova.js, but
> this file is missing in the eclipse project. I assume eclipse automagically
> adds it when the project is built.
> Ive removed the send, variant and variant secret - to protect the identity
> of the innocent.
>
> <!DOCTYPE HTML>
> <html>
> <head>
>   <title>Demo</title>
> </head>
> <body>
>
> <script type="text/javascript" charset="utf-8" src="cordova.js"></script>
> <script type="text/javascript" charset="utf-8"
> src="jquery_1.5.2.min.js"></script>
>
> <script type="text/javascript">
>
> var app = {
>  // Application Constructor
>  initialize: function() {
>    this.bindEvents();
>  },
>  // Bind Event Listeners
>  //
>  // Bind any events that are required on startup. Common events are:
>  // 'load', 'deviceready', 'offline', and 'online'.
>  bindEvents: function() {
>    document.addEventListener('deviceready', this.onDeviceReady, false);
>  },
>  // deviceready Event Handler
>  //
>  // The scope of 'this' is the event. In order to call the 'receivedEvent'
>  // function, we must explicitly call 'app.receivedEvent(...);'
>  onDeviceReady: function() {
>    app.receivedEvent('deviceready');
>    var pushConfig = {
>      pushServerURL: "http://192.168.1.40:8080/ag-push/",
>      android: {
>        senderID: "",
>        variantID: "",
>        variantSecret: ""
>      }
>    };
> push.register(app.onNotification, successHandler, errorHandler,
> pushConfig);
>
> function successHandler() {
>  console.log('success')
> }
>
> function errorHandler(message) {
>  console.log('error ' + message);
> }
> },
> onNotification: function(event) {
>  alert(event.alert);
> },
> // Update DOM on a Received Event
> receivedEvent: function(id) {
>  var parentElement = document.getElementById(id);
>  var listeningElement = parentElement.querySelector('.listening');
>  var receivedElement = parentElement.querySelector('.received');
>
>  listeningElement.setAttribute('style', 'display:none;');
>  receivedElement.setAttribute('style', 'display:block;');
>
>  console.log('Received Event: ' + id);
> }
> };
>
> app.initialize();
>
>   document.addEventListener('deviceready', onDeviceReady, true);
>
> </script>
> <div id="home">
>   <div id="app-status-div">
>     <ul id="app-status-ul">
>       <li>AeroGear PushPlugin Unified Push Demo</li>
>     </ul>
>   </div>
> </div>
> </body>
> </html>
>
> Can anyone see anything obviously wrong?
>
> How does one debug in such a situation?
>
> Thanks
>
>
> On Sat, Jan 23, 2016 at 12:21 AM, Anton Hughes <kurrent93 at gmail.com>
> wrote:
>
>> Ok, I have managed to get setup with Genymotion, and have the google
>> tools installed.
>>
>> How, then, can I deploy the cordova project to the genymotion vm? Is
>> there a way to do that from within Eclipse?
>>
>> Thanks
>>
>> On Fri, Jan 22, 2016 at 2:35 PM, Anton Hughes <kurrent93 at gmail.com>
>> wrote:
>>
>>> Thanks Luke. I will try this.
>>>
>>> On Fri, Jan 22, 2016 at 2:31 PM, Luke Holmquist <lholmqui at redhat.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Fri, Jan 22, 2016 at 8:28 AM, Anton Hughes <kurrent93 at gmail.com>
>>>> wrote:
>>>>
>>>>>
>>>>> On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com>
>>>>> wrote:
>>>>>
>>>>>> just a thought that popped into my head.   The url pointing to your
>>>>>> UPS server shouldn't be localhost, since there is no localhost on the
>>>>>> device.  not sure if thats how you have it configured, though. but this
>>>>>> always bites me
>>>>>
>>>>>
>>>>> The wise expression of Homer Simpson comes rushing into mind!
>>>>> I'm away from my dev environment, so cannot test - but, yes I am using
>>>>> localhost in the cordova project.
>>>>>
>>>>> So if not localhost, then what?
>>>>>
>>>> if you are running the UPS server on your local machine, then it would
>>>> be your IP instead of localhost.  The device just needs to "see" it, so
>>>> that means you need to be on the same network.   unless you are running it
>>>> in the cloud or something
>>>>
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/95b18559/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 31767 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/95b18559/attachment-0001.png 

From kurrent93 at gmail.com  Sat Jan 23 04:53:49 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Sat, 23 Jan 2016 10:53:49 +0100
Subject: [Aerogear-users] Testing push in Cordova
In-Reply-To: <CAD44pJD+iCU1FHn7HZWgzZ=4dqJNr48k1ayFE2GRAZrrO_GZug@mail.gmail.com>
References: <CAD44pJA8c=RJ-X+TMvbr51Fpec7ZdDMM5wgTfCijBU21wZkcBg@mail.gmail.com>
	<CALD3Fd1=VyynymETmme=tBhfrZhLbhFHbim_v02yQdrQqPH7TQ@mail.gmail.com>
	<CAD44pJAgqtnF3cez_dZc39YmW9aYPwWDGmnvR9Oa1vXST0KJWA@mail.gmail.com>
	<CALD3Fd3g7XYRKyQWZLMMF0ZzEQ9fhFh+TtLiEGbrOLaCFAf4qQ@mail.gmail.com>
	<CAD44pJC3BmrmUUCGyNEata+aRhUm32WxhtWgdkec0Q9WphcxbA@mail.gmail.com>
	<CAD44pJBx6wiLjytDiqDWM6Oq=tgzjNpaixXO0DFviVF0c1godA@mail.gmail.com>
	<CAD44pJDwLDSccxf9paL7KLLhKsgD+EHCMT1nVGHWODQ-cOREDg@mail.gmail.com>
	<CAD44pJD+iCU1FHn7HZWgzZ=4dqJNr48k1ayFE2GRAZrrO_GZug@mail.gmail.com>
Message-ID: <CAD44pJCUKR7uWYPewFvnJTkhmwdDng9W_AROvHGfTn3Cx-rH-Q@mail.gmail.com>

Let me start a new thread for this issue.
Thanks

On Sat, Jan 23, 2016 at 1:51 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Ok, I found the problem (see below) - but not the solution.
>
> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear.ajax.js
> Failed to load resource: net::ERR_FILE_NOT_FOUND
> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear-push.js
> Failed to load resource: net::ERR_FILE_NOT_FOUND
> cordova.js:1418 Uncaught Error: Module aerogear-cordova-push.AeroGear.ajax
> does not exist.
> cordova.js:1183 deviceready has not fired after 5 seconds.
> cordova.js:1176 Channel not fired: onPluginsReady
> cordova.js:1176 Channel not fired: onCordovaReady
>
> The resources that failed to load are present in the project.
> [image: Inline image 1]
>
> On Sat, Jan 23, 2016 at 12:51 AM, Anton Hughes <kurrent93 at gmail.com>
> wrote:
>
>> Ok so I managed to deploy my cordova app onto genymotion. Actually that
>> wasnt too difficult.
>> But, alas, it still does not connect to the UPS.
>>
>> I have updated the pushServerURL value to use my hosts ip.
>>
>> My index.html looks like this - I notice it is referencing cordova.js,
>> but this file is missing in the eclipse project. I assume eclipse
>> automagically adds it when the project is built.
>> Ive removed the send, variant and variant secret - to protect the
>> identity of the innocent.
>>
>> <!DOCTYPE HTML>
>> <html>
>> <head>
>>   <title>Demo</title>
>> </head>
>> <body>
>>
>> <script type="text/javascript" charset="utf-8" src="cordova.js"></script>
>> <script type="text/javascript" charset="utf-8"
>> src="jquery_1.5.2.min.js"></script>
>>
>> <script type="text/javascript">
>>
>> var app = {
>>  // Application Constructor
>>  initialize: function() {
>>    this.bindEvents();
>>  },
>>  // Bind Event Listeners
>>  //
>>  // Bind any events that are required on startup. Common events are:
>>  // 'load', 'deviceready', 'offline', and 'online'.
>>  bindEvents: function() {
>>    document.addEventListener('deviceready', this.onDeviceReady, false);
>>  },
>>  // deviceready Event Handler
>>  //
>>  // The scope of 'this' is the event. In order to call the 'receivedEvent'
>>  // function, we must explicitly call 'app.receivedEvent(...);'
>>  onDeviceReady: function() {
>>    app.receivedEvent('deviceready');
>>    var pushConfig = {
>>      pushServerURL: "http://192.168.1.40:8080/ag-push/",
>>      android: {
>>        senderID: "",
>>        variantID: "",
>>        variantSecret: ""
>>      }
>>    };
>> push.register(app.onNotification, successHandler, errorHandler,
>> pushConfig);
>>
>> function successHandler() {
>>  console.log('success')
>> }
>>
>> function errorHandler(message) {
>>  console.log('error ' + message);
>> }
>> },
>> onNotification: function(event) {
>>  alert(event.alert);
>> },
>> // Update DOM on a Received Event
>> receivedEvent: function(id) {
>>  var parentElement = document.getElementById(id);
>>  var listeningElement = parentElement.querySelector('.listening');
>>  var receivedElement = parentElement.querySelector('.received');
>>
>>  listeningElement.setAttribute('style', 'display:none;');
>>  receivedElement.setAttribute('style', 'display:block;');
>>
>>  console.log('Received Event: ' + id);
>> }
>> };
>>
>> app.initialize();
>>
>>   document.addEventListener('deviceready', onDeviceReady, true);
>>
>> </script>
>> <div id="home">
>>   <div id="app-status-div">
>>     <ul id="app-status-ul">
>>       <li>AeroGear PushPlugin Unified Push Demo</li>
>>     </ul>
>>   </div>
>> </div>
>> </body>
>> </html>
>>
>> Can anyone see anything obviously wrong?
>>
>> How does one debug in such a situation?
>>
>> Thanks
>>
>>
>> On Sat, Jan 23, 2016 at 12:21 AM, Anton Hughes <kurrent93 at gmail.com>
>> wrote:
>>
>>> Ok, I have managed to get setup with Genymotion, and have the google
>>> tools installed.
>>>
>>> How, then, can I deploy the cordova project to the genymotion vm? Is
>>> there a way to do that from within Eclipse?
>>>
>>> Thanks
>>>
>>> On Fri, Jan 22, 2016 at 2:35 PM, Anton Hughes <kurrent93 at gmail.com>
>>> wrote:
>>>
>>>> Thanks Luke. I will try this.
>>>>
>>>> On Fri, Jan 22, 2016 at 2:31 PM, Luke Holmquist <lholmqui at redhat.com>
>>>> wrote:
>>>>
>>>>>
>>>>>
>>>>> On Fri, Jan 22, 2016 at 8:28 AM, Anton Hughes <kurrent93 at gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>> On Fri, Jan 22, 2016 at 2:25 PM, Luke Holmquist <lholmqui at redhat.com>
>>>>>> wrote:
>>>>>>
>>>>>>> just a thought that popped into my head.   The url pointing to your
>>>>>>> UPS server shouldn't be localhost, since there is no localhost on the
>>>>>>> device.  not sure if thats how you have it configured, though. but this
>>>>>>> always bites me
>>>>>>
>>>>>>
>>>>>> The wise expression of Homer Simpson comes rushing into mind!
>>>>>> I'm away from my dev environment, so cannot test - but, yes I am
>>>>>> using localhost in the cordova project.
>>>>>>
>>>>>> So if not localhost, then what?
>>>>>>
>>>>> if you are running the UPS server on your local machine, then it would
>>>>> be your IP instead of localhost.  The device just needs to "see" it, so
>>>>> that means you need to be on the same network.   unless you are running it
>>>>> in the cloud or something
>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/368cb36f/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 31767 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/368cb36f/attachment-0001.png 

From kurrent93 at gmail.com  Sat Jan 23 04:55:37 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Sat, 23 Jan 2016 10:55:37 +0100
Subject: [Aerogear-users] Failed to load resource
Message-ID: <CAD44pJDZdfFTGS1j5kMC0M_0wLM4k12Axkz37kbZW+v-RrrFmA@mail.gmail.com>

Hello

I am followig the guide on
https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/ -
and have gone through this a few times now, so I am sure I am not missing
any step.

I am deploying my sample app onto genymotion, and using the chrome
debugger, and I see the following error:

file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear.ajax.js
Failed to load resource: net::ERR_FILE_NOT_FOUND
file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear-push.js
Failed to load resource: net::ERR_FILE_NOT_FOUND
cordova.js:1431 Uncaught Error: Module aerogear-cordova-push.AeroGear.ajax
does not exist.
cordova.js:1185 deviceready has not fired after 5 seconds.
cordova.js:1178 Channel not fired: onPluginsReady
cordova.js:1178 Channel not fired: onCordovaReady

How can I fix this?

Thamks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/75e66e35/attachment.html 

From kurrent93 at gmail.com  Sat Jan 23 15:14:09 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Sat, 23 Jan 2016 21:14:09 +0100
Subject: [Aerogear-users] Failed to load resource
In-Reply-To: <CAD44pJDZdfFTGS1j5kMC0M_0wLM4k12Axkz37kbZW+v-RrrFmA@mail.gmail.com>
References: <CAD44pJDZdfFTGS1j5kMC0M_0wLM4k12Axkz37kbZW+v-RrrFmA@mail.gmail.com>
Message-ID: <CAD44pJAnatBhB4n9j1CRx0-nYzc_TKBvqgcxis47UY0tf_OCUw@mail.gmail.com>

I have added more details, regarding this issue, to
http://stackoverflow.com/questions/34962768/failed-to-load-resource-neterr-file-not-found-with-cordova
.

Thanks

On Sat, Jan 23, 2016 at 10:55 AM, Anton Hughes <kurrent93 at gmail.com> wrote:

> Hello
>
> I am followig the guide on
> https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/ -
> and have gone through this a few times now, so I am sure I am not missing
> any step.
>
> I am deploying my sample app onto genymotion, and using the chrome
> debugger, and I see the following error:
>
> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear.ajax.js
> Failed to load resource: net::ERR_FILE_NOT_FOUND
> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear-push.js
> Failed to load resource: net::ERR_FILE_NOT_FOUND
> cordova.js:1431 Uncaught Error: Module aerogear-cordova-push.AeroGear.ajax
> does not exist.
> cordova.js:1185 deviceready has not fired after 5 seconds.
> cordova.js:1178 Channel not fired: onPluginsReady
> cordova.js:1178 Channel not fired: onCordovaReady
>
> How can I fix this?
>
> Thamks
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160123/d04ca188/attachment.html 

From edewit at redhat.com  Mon Jan 25 03:37:25 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Mon, 25 Jan 2016 09:37:25 +0100
Subject: [Aerogear-users] Failed to load resource
In-Reply-To: <CAD44pJAnatBhB4n9j1CRx0-nYzc_TKBvqgcxis47UY0tf_OCUw@mail.gmail.com>
References: <CAD44pJDZdfFTGS1j5kMC0M_0wLM4k12Axkz37kbZW+v-RrrFmA@mail.gmail.com>
	<CAD44pJAnatBhB4n9j1CRx0-nYzc_TKBvqgcxis47UY0tf_OCUw@mail.gmail.com>
Message-ID: <CAO2B-fZ9Ld6tJzuP5VRzPSuAXRGixfDi8Ert9fL6o5eixyC2aA@mail.gmail.com>

Strange error the files are empty and not found? Could you try it from the
command line?

cordova create push-test
cd push-test
cordova plugin add aerogear-cordova-push
cordova platform add android
cordova run

both files should be found and not empty. Aerogear-push.js is the
javascript interface to the plugin's native parts so that must be there
otherwise it will not work. What could be the case is that you don't have
cordova.js as a javascript reference in your project?

Hope this helps,

On Sat, Jan 23, 2016 at 9:14 PM, Anton Hughes <kurrent93 at gmail.com> wrote:

> I have added more details, regarding this issue, to
> http://stackoverflow.com/questions/34962768/failed-to-load-resource-neterr-file-not-found-with-cordova
> .
>
> Thanks
>
> On Sat, Jan 23, 2016 at 10:55 AM, Anton Hughes <kurrent93 at gmail.com>
> wrote:
>
>> Hello
>>
>> I am followig the guide on
>> https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/ -
>> and have gone through this a few times now, so I am sure I am not missing
>> any step.
>>
>> I am deploying my sample app onto genymotion, and using the chrome
>> debugger, and I see the following error:
>>
>> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear.ajax.js
>> Failed to load resource: net::ERR_FILE_NOT_FOUND
>> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear-push.js
>> Failed to load resource: net::ERR_FILE_NOT_FOUND
>> cordova.js:1431 Uncaught Error: Module
>> aerogear-cordova-push.AeroGear.ajax does not exist.
>> cordova.js:1185 deviceready has not fired after 5 seconds.
>> cordova.js:1178 Channel not fired: onPluginsReady
>> cordova.js:1178 Channel not fired: onCordovaReady
>>
>> How can I fix this?
>>
>> Thamks
>>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160125/656f8051/attachment.html 

From aamagdi at ejada.com  Mon Jan 25 06:51:35 2016
From: aamagdi at ejada.com (aamagdi)
Date: Mon, 25 Jan 2016 04:51:35 -0700 (MST)
Subject: [Aerogear-users]  Pending Notification Keep loading forever
Message-ID: <1453722695250-490.post@n5.nabble.com>

Hi

When I send a notification and it has no receivers for example specify alias
that doesn't exit, in the notification Activity Log it keep the entry as
pending forever as per the below shot, is there a way to stop the pending
status of the notification

<http://aerogear-users.1116366.n5.nabble.com/file/n490/pending.png> 

<http://aerogear-users.1116366.n5.nabble.com/file/n490/pending2.png> 



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Pending-Notification-Keep-loading-forever-tp490.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From kurrent93 at gmail.com  Mon Jan 25 06:58:22 2016
From: kurrent93 at gmail.com (Anton Hughes)
Date: Mon, 25 Jan 2016 12:58:22 +0100
Subject: [Aerogear-users] Failed to load resource
In-Reply-To: <CAO2B-fZ9Ld6tJzuP5VRzPSuAXRGixfDi8Ert9fL6o5eixyC2aA@mail.gmail.com>
References: <CAD44pJDZdfFTGS1j5kMC0M_0wLM4k12Axkz37kbZW+v-RrrFmA@mail.gmail.com>
	<CAD44pJAnatBhB4n9j1CRx0-nYzc_TKBvqgcxis47UY0tf_OCUw@mail.gmail.com>
	<CAO2B-fZ9Ld6tJzuP5VRzPSuAXRGixfDi8Ert9fL6o5eixyC2aA@mail.gmail.com>
Message-ID: <CAD44pJC_v+r2D1+RFdV22H_=j445FEDhiADWs=ThXmyAJob4vA@mail.gmail.com>

Thanks for your help Erik

I dont know what the problem was -  but a restart seems to have fixed it.

Crazy.

On Mon, Jan 25, 2016 at 9:37 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Strange error the files are empty and not found? Could you try it from the
> command line?
>
> cordova create push-test
> cd push-test
> cordova plugin add aerogear-cordova-push
> cordova platform add android
> cordova run
>
> both files should be found and not empty. Aerogear-push.js is the
> javascript interface to the plugin's native parts so that must be there
> otherwise it will not work. What could be the case is that you don't have
> cordova.js as a javascript reference in your project?
>
> Hope this helps,
>
> On Sat, Jan 23, 2016 at 9:14 PM, Anton Hughes <kurrent93 at gmail.com> wrote:
>
>> I have added more details, regarding this issue, to
>> http://stackoverflow.com/questions/34962768/failed-to-load-resource-neterr-file-not-found-with-cordova
>> .
>>
>> Thanks
>>
>> On Sat, Jan 23, 2016 at 10:55 AM, Anton Hughes <kurrent93 at gmail.com>
>> wrote:
>>
>>> Hello
>>>
>>> I am followig the guide on
>>> https://aerogear.org/docs/guides/aerogear-cordova/AerogearCordovaPush/
>>> - and have gone through this a few times now, so I am sure I am not missing
>>> any step.
>>>
>>> I am deploying my sample app onto genymotion, and using the chrome
>>> debugger, and I see the following error:
>>>
>>> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear.ajax.js
>>> Failed to load resource: net::ERR_FILE_NOT_FOUND
>>> file:///android_asset/www/plugins/aerogear-cordova-push/www/aerogear-push.js
>>> Failed to load resource: net::ERR_FILE_NOT_FOUND
>>> cordova.js:1431 Uncaught Error: Module
>>> aerogear-cordova-push.AeroGear.ajax does not exist.
>>> cordova.js:1185 deviceready has not fired after 5 seconds.
>>> cordova.js:1178 Channel not fired: onPluginsReady
>>> cordova.js:1178 Channel not fired: onCordovaReady
>>>
>>> How can I fix this?
>>>
>>> Thamks
>>>
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Cheers,
>        Erik Jan
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160125/a67f5c9d/attachment-0001.html 

From staffan.mattsson at gmail.com  Tue Jan 26 08:56:44 2016
From: staffan.mattsson at gmail.com (Staffan Mattsson)
Date: Tue, 26 Jan 2016 14:56:44 +0100
Subject: [Aerogear-users] Hello and Compile help
Message-ID: <CAErOWT6ubdGhTbPMQ8Ff=_b7Jeos3SsfjJY7dX2v8ygXVE3cXA@mail.gmail.com>

Hello everyone,
My name is staffan and Im a hobby developer. :) No status, but pure fun.
I've heard that this list also works as some kind of support forum. I hope
thats right...

It seems I cannot succed in compiling AeroGearHttp needed for
AeroGearOAuth2.
When I compile only AeroGearOAuth2 i get the error: module AeroGearHttp not
found,
which is ok. I can understand that. But then when I download AeroGearHttp
and try to compile that I get all kind of error. Im not even sure that he
tries to compile in the correct (swift) language, because the errors are
really strange. They sort of miss the swift structure I think.

I would like to thank for a great library, but I havent tried it yet. :)

/Staffan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160126/d7f46ed0/attachment.html 

From scm.blanc at gmail.com  Wed Jan 27 09:44:32 2016
From: scm.blanc at gmail.com (Sebastien Blanc)
Date: Wed, 27 Jan 2016 15:44:32 +0100
Subject: [Aerogear-users] Staging of UnifiedPush Server 1.1.1
Message-ID: <CAD_dpu1dVQeEAmDL6Mp1QnvGfCaD-EFZxObotxVLmQ=DOb3vuQ@mail.gmail.com>

Hi Folk,

I'm happy to announce that UPS 1.1.1 has been staged  :

https://repository.jboss.org/nexus/content/repositories/jboss_releases_staging_profile-7587

Release notes can be found here :

https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12313724&version=12327457&_sscc=t

Please give it a try, I plan to hit the magic button Friday end of the day.

Sebi
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160127/0c1da3a2/attachment.html 

From edewit at redhat.com  Fri Jan 29 07:02:30 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 29 Jan 2016 13:02:30 +0100
Subject: [Aerogear-users] Oauth2 cordova plugin release
Message-ID: <CAO2B-fYX+4i5-nU2Nr-idNoj2y=cbXT=Q3naX1LS=VEVfD-1WQ@mail.gmail.com>

Hi,

We would like to release a new version of the oauth2 cordova plugin the
current fixed issue are:
Bug

   - [AGCORDOVA-114 <https://issues.jboss.org/browse/AGCORDOVA-114>] -
   promise plugin can not be found

Enhancement

   - [AGCORDOVA-91 <https://issues.jboss.org/browse/AGCORDOVA-91>] - update
   oauth2 ios lib to swift 2


-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160129/5cf65b0c/attachment.html 

From edewit at redhat.com  Fri Jan 29 10:25:21 2016
From: edewit at redhat.com (Erik Jan de Wit)
Date: Fri, 29 Jan 2016 16:25:21 +0100
Subject: [Aerogear-users] Oauth2 cordova plugin release
In-Reply-To: <CAO2B-fYX+4i5-nU2Nr-idNoj2y=cbXT=Q3naX1LS=VEVfD-1WQ@mail.gmail.com>
References: <CAO2B-fYX+4i5-nU2Nr-idNoj2y=cbXT=Q3naX1LS=VEVfD-1WQ@mail.gmail.com>
Message-ID: <CAO2B-fazeotjeH2KY37OvP3snAu4oC8eAFqiJMPTbyiQjrhyQA@mail.gmail.com>

forgot to mention that like always there is a release branch you can use to
test the release:

https://github.com/aerogear/aerogear-cordova-oauth2/tree/release

On Fri, Jan 29, 2016 at 1:02 PM, Erik Jan de Wit <edewit at redhat.com> wrote:

> Hi,
>
> We would like to release a new version of the oauth2 cordova plugin the
> current fixed issue are:
> Bug
>
>    - [AGCORDOVA-114 <https://issues.jboss.org/browse/AGCORDOVA-114>] -
>    promise plugin can not be found
>
> Enhancement
>
>    - [AGCORDOVA-91 <https://issues.jboss.org/browse/AGCORDOVA-91>] -
>    update oauth2 ios lib to swift 2
>
>
> --
> Cheers,
>        Erik Jan
>



-- 
Cheers,
       Erik Jan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160129/2d1cdcae/attachment.html 

From yves.nicolas at dynamease.com  Fri Jan 29 12:01:58 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Fri, 29 Jan 2016 10:01:58 -0700 (MST)
Subject: [Aerogear-users] Unexpected stops for Unified push server
Message-ID: <1454086918832-496.post@n5.nabble.com>

I get unexpected stops from Aerogear push server which I can not explain or
relate to the application using the server. This can happen anytime after
several days or even weeks of correct operations.

Here is the traces I got leading to the stop. Any hint?

21:59:57,034 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2)
JBAS017535: Unregistered web context: /auth
21:59:57,041 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2)
JBAS017521: Undertow HTTPS listener https suspending
21:59:57,041 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2)
JBAS017520: Undertow HTTPS listener https stopped, was bound to
/0.0.0.0:8443
21:59:57,048 WARN 
[org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService
Thread Pool -- 102) IJ000615: Destroying active connection in pool:
KeycloakDS
(org.jboss.jca.adapters.jdbc.local.LocalManagedConnection at 60bf23dd)
21:59:57,100 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-2)
JBAS017532: Host default-host stopping
21:59:57,187 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-2)
JBAS015877: Stopped deployment auth-server.war (runtime-name:
auth-server.war) in 197ms
21:59:57,196 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 76)
JBAS011410: Stopping Persistence Unit (phase 2 of 2) Service
'ag-push.war#unifiedpush-default'
21:59:57,203 INFO  [org.jboss.as.messaging] (MSC service thread 1-2)
JBAS011605: Unbound messaging object to jndi name
java:jboss/DefaultJMSConnectionFactory
21:59:57,204 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC
service thread 1-1) JBAS010409: Unbound data source
[java:jboss/datasources/ExampleDS]
21:59:57,208 INFO  [org.jboss.as.messaging] (ServerService Thread Pool --
82) JBAS011605: Unbound messaging object to jndi name
java:/queue/AdmPushMessageQueue
21:59:57,208 INFO  [org.jboss.as.connector.deployment] (MSC service thread
1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
21:59:57,209 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1)
JBAS016009: Stopping weld service for deployment ag-push.war
21:59:57,220 INFO  [org.jboss.as.messaging] (ServerService Thread Pool --
98) JBAS011605: Unbound messaging object to jndi name
java:/queue/SimplePushTokenBatchQueue
21:59:57,222 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service
thread 1-2) JBAS010418: Stopped Driver service with driver-name = h2
21:59:57,225 INFO  [org.hornetq.ra] (ServerService Thread Pool -- 84)
HQ151003: HornetQ resource adaptor stopped
21:59:57,250 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 86)
JBAS011410: Stopping Persistence Unit (phase 1 of 2) Service
'ag-push.war#unifiedpush-default'
21:59:57,251 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC
service thread 1-1) JBAS010409: Unbound data source
[java:jboss/datasources/UnifiedPushDS]
21:59:57,252 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service
thread 1-1) JBAS010418: Stopped Driver service with driver-name = mysqlup
21:59:57,292 INFO  [org.jboss.as.server.deployment] (MSC service thread 1-1)
JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) in
302ms
21:59:57,386 INFO  [org.hornetq.core.server] (ServerService Thread Pool --
84) HQ221002: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124)
[122fa8b6-5eb6-11e5-a98b-738666e7f990] stopped
21:59:57,387 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1)
JBAS017521: Undertow HTTP listener default suspending
21:59:57,387 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1)
JBAS017520: Undertow HTTP listener default stopped, was bound to
/0.0.0.0:8080
21:59:57,394 INFO  [org.wildfly.extension.undertow] (MSC service thread 1-1)
JBAS017506: Undertow 1.1.8.Final stopping
21:59:57,408 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950:
WildFly 8.2.1.Final "Tweek" stopped in 415ms




--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-stops-for-Unified-push-server-tp496.html
Sent from the aerogear-users mailing list archive at Nabble.com.

From lholmqui at redhat.com  Fri Jan 29 12:39:47 2016
From: lholmqui at redhat.com (Luke Holmquist)
Date: Fri, 29 Jan 2016 12:39:47 -0500
Subject: [Aerogear-users] Unexpected stops for Unified push server
In-Reply-To: <1454086918832-496.post@n5.nabble.com>
References: <1454086918832-496.post@n5.nabble.com>
Message-ID: <CALD3Fd1rR1vV=yyE6zAZFzG4tLgbmR=w3KLoQAsJSzzXx-6vHA@mail.gmail.com>

are you running this on open shift, or "local" and by local i mean, not on
openshift

On Fri, Jan 29, 2016 at 12:01 PM, Yves Nicolas <yves.nicolas at dynamease.com>
wrote:

> I get unexpected stops from Aerogear push server which I can not explain or
> relate to the application using the server. This can happen anytime after
> several days or even weeks of correct operations.
>
> Here is the traces I got leading to the stop. Any hint?
>
> 21:59:57,034 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-2)
> JBAS017535: Unregistered web context: /auth
> 21:59:57,041 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-2)
> JBAS017521: Undertow HTTPS listener https suspending
> 21:59:57,041 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-2)
> JBAS017520: Undertow HTTPS listener https stopped, was bound to
> /0.0.0.0:8443
> 21:59:57,048 WARN
> [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool] (ServerService
> Thread Pool -- 102) IJ000615: Destroying active connection in pool:
> KeycloakDS
> (org.jboss.jca.adapters.jdbc.local.LocalManagedConnection at 60bf23dd)
> 21:59:57,100 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-2)
> JBAS017532: Host default-host stopping
> 21:59:57,187 INFO  [org.jboss.as.server.deployment] (MSC service thread
> 1-2)
> JBAS015877: Stopped deployment auth-server.war (runtime-name:
> auth-server.war) in 197ms
> 21:59:57,196 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 76)
> JBAS011410: Stopping Persistence Unit (phase 2 of 2) Service
> 'ag-push.war#unifiedpush-default'
> 21:59:57,203 INFO  [org.jboss.as.messaging] (MSC service thread 1-2)
> JBAS011605: Unbound messaging object to jndi name
> java:jboss/DefaultJMSConnectionFactory
> 21:59:57,204 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC
> service thread 1-1) JBAS010409: Unbound data source
> [java:jboss/datasources/ExampleDS]
> 21:59:57,208 INFO  [org.jboss.as.messaging] (ServerService Thread Pool --
> 82) JBAS011605: Unbound messaging object to jndi name
> java:/queue/AdmPushMessageQueue
> 21:59:57,208 INFO  [org.jboss.as.connector.deployment] (MSC service thread
> 1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
> 21:59:57,209 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1)
> JBAS016009: Stopping weld service for deployment ag-push.war
> 21:59:57,220 INFO  [org.jboss.as.messaging] (ServerService Thread Pool --
> 98) JBAS011605: Unbound messaging object to jndi name
> java:/queue/SimplePushTokenBatchQueue
> 21:59:57,222 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service
> thread 1-2) JBAS010418: Stopped Driver service with driver-name = h2
> 21:59:57,225 INFO  [org.hornetq.ra] (ServerService Thread Pool -- 84)
> HQ151003: HornetQ resource adaptor stopped
> 21:59:57,250 INFO  [org.jboss.as.jpa] (ServerService Thread Pool -- 86)
> JBAS011410: Stopping Persistence Unit (phase 1 of 2) Service
> 'ag-push.war#unifiedpush-default'
> 21:59:57,251 INFO  [org.jboss.as.connector.subsystems.datasources] (MSC
> service thread 1-1) JBAS010409: Unbound data source
> [java:jboss/datasources/UnifiedPushDS]
> 21:59:57,252 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC service
> thread 1-1) JBAS010418: Stopped Driver service with driver-name = mysqlup
> 21:59:57,292 INFO  [org.jboss.as.server.deployment] (MSC service thread
> 1-1)
> JBAS015877: Stopped deployment ag-push.war (runtime-name: ag-push.war) in
> 302ms
> 21:59:57,386 INFO  [org.hornetq.core.server] (ServerService Thread Pool --
> 84) HQ221002: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124)
> [122fa8b6-5eb6-11e5-a98b-738666e7f990] stopped
> 21:59:57,387 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-1)
> JBAS017521: Undertow HTTP listener default suspending
> 21:59:57,387 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-1)
> JBAS017520: Undertow HTTP listener default stopped, was bound to
> /0.0.0.0:8080
> 21:59:57,394 INFO  [org.wildfly.extension.undertow] (MSC service thread
> 1-1)
> JBAS017506: Undertow 1.1.8.Final stopping
> 21:59:57,408 INFO  [org.jboss.as] (MSC service thread 1-2) JBAS015950:
> WildFly 8.2.1.Final "Tweek" stopped in 415ms
>
>
>
>
> --
> View this message in context:
> http://aerogear-users.1116366.n5.nabble.com/Unexpected-stops-for-Unified-push-server-tp496.html
> Sent from the aerogear-users mailing list archive at Nabble.com.
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160129/552fd754/attachment-0001.html 

From yves.nicolas at dynamease.com  Sat Jan 30 05:14:30 2016
From: yves.nicolas at dynamease.com (Yves Nicolas)
Date: Sat, 30 Jan 2016 03:14:30 -0700 (MST)
Subject: [Aerogear-users] Unexpected stops for Unified push server
In-Reply-To: <CALD3Fd1rR1vV=yyE6zAZFzG4tLgbmR=w3KLoQAsJSzzXx-6vHA@mail.gmail.com>
References: <1454086918832-496.post@n5.nabble.com>
	<CALD3Fd1rR1vV=yyE6zAZFzG4tLgbmR=w3KLoQAsJSzzXx-6vHA@mail.gmail.com>
Message-ID: <56AC8CF1.10903@dynamease.com>

Not running on openshift.
Running on a debian jessie distribution on a xen virtual machine running 
on a dedicated server.. Database is mysql that runs inside a docker 
container with 3306 port exposed
Wildfly itself runs directly on debian, nothing else than aerogear runs 
on this virtual machine

Le 29/01/2016 18:40, Luke Holmquist [via aerogear-users] a ?crit :
> are you running this on open shift, or "local" and by local i mean, 
> not on openshift
>
> On Fri, Jan 29, 2016 at 12:01 PM, Yves Nicolas <[hidden email] 
> </user/SendEmail.jtp?type=node&node=497&i=0>> wrote:
>
>     I get unexpected stops from Aerogear push server which I can not
>     explain or
>     relate to the application using the server. This can happen
>     anytime after
>     several days or even weeks of correct operations.
>
>     Here is the traces I got leading to the stop. Any hint?
>
>     21:59:57,034 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-2)
>     JBAS017535: Unregistered web context: /auth
>     21:59:57,041 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-2)
>     JBAS017521: Undertow HTTPS listener https suspending
>     21:59:57,041 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-2)
>     JBAS017520: Undertow HTTPS listener https stopped, was bound to
>     /0.0.0.0:8443 <http://0.0.0.0:8443>
>     21:59:57,048 WARN
>     [org.jboss.jca.core.connectionmanager.pool.strategy.OnePool]
>     (ServerService
>     Thread Pool -- 102) IJ000615: Destroying active connection in pool:
>     KeycloakDS
>     (org.jboss.jca.adapters.jdbc.local.LocalManagedConnection at 60bf23dd)
>     21:59:57,100 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-2)
>     JBAS017532: Host default-host stopping
>     21:59:57,187 INFO  [org.jboss.as.server.deployment] (MSC service
>     thread 1-2)
>     JBAS015877: Stopped deployment auth-server.war (runtime-name:
>     auth-server.war) in 197ms
>     21:59:57,196 INFO  [org.jboss.as.jpa] (ServerService Thread Pool
>     -- 76)
>     JBAS011410: Stopping Persistence Unit (phase 2 of 2) Service
>     'ag-push.war#unifiedpush-default'
>     21:59:57,203 INFO  [org.jboss.as.messaging] (MSC service thread 1-2)
>     JBAS011605: Unbound messaging object to jndi name
>     java:jboss/DefaultJMSConnectionFactory
>     21:59:57,204 INFO [org.jboss.as.connector.subsystems.datasources] (MSC
>     service thread 1-1) JBAS010409: Unbound data source
>     [java:jboss/datasources/ExampleDS]
>     21:59:57,208 INFO  [org.jboss.as.messaging] (ServerService Thread
>     Pool --
>     82) JBAS011605: Unbound messaging object to jndi name
>     java:/queue/AdmPushMessageQueue
>     21:59:57,208 INFO  [org.jboss.as.connector.deployment] (MSC
>     service thread
>     1-1) JBAS010410: Unbound JCA ConnectionFactory [java:/JmsXA]
>     21:59:57,209 INFO  [org.jboss.weld.deployer] (MSC service thread 1-1)
>     JBAS016009: Stopping weld service for deployment ag-push.war
>     21:59:57,220 INFO  [org.jboss.as.messaging] (ServerService Thread
>     Pool --
>     98) JBAS011605: Unbound messaging object to jndi name
>     java:/queue/SimplePushTokenBatchQueue
>     21:59:57,222 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC
>     service
>     thread 1-2) JBAS010418: Stopped Driver service with driver-name = h2
>     21:59:57,225 INFO  [org.hornetq.ra] (ServerService Thread Pool -- 84)
>     HQ151003: HornetQ resource adaptor stopped
>     21:59:57,250 INFO  [org.jboss.as.jpa] (ServerService Thread Pool
>     -- 86)
>     JBAS011410: Stopping Persistence Unit (phase 1 of 2) Service
>     'ag-push.war#unifiedpush-default'
>     21:59:57,251 INFO [org.jboss.as.connector.subsystems.datasources] (MSC
>     service thread 1-1) JBAS010409: Unbound data source
>     [java:jboss/datasources/UnifiedPushDS]
>     21:59:57,252 INFO  [org.jboss.as.connector.deployers.jdbc] (MSC
>     service
>     thread 1-1) JBAS010418: Stopped Driver service with driver-name =
>     mysqlup
>     21:59:57,292 INFO  [org.jboss.as.server.deployment] (MSC service
>     thread 1-1)
>     JBAS015877: Stopped deployment ag-push.war (runtime-name:
>     ag-push.war) in
>     302ms
>     21:59:57,386 INFO  [org.hornetq.core.server] (ServerService Thread
>     Pool --
>     84) HQ221002: HornetQ Server version 2.4.5.FINAL (Wild Hornet, 124)
>     [122fa8b6-5eb6-11e5-a98b-738666e7f990] stopped
>     21:59:57,387 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-1)
>     JBAS017521: Undertow HTTP listener default suspending
>     21:59:57,387 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-1)
>     JBAS017520: Undertow HTTP listener default stopped, was bound to
>     /0.0.0.0:8080 <http://0.0.0.0:8080>
>     21:59:57,394 INFO  [org.wildfly.extension.undertow] (MSC service
>     thread 1-1)
>     JBAS017506: Undertow 1.1.8.Final stopping
>     21:59:57,408 INFO  [org.jboss.as <http://org.jboss.as>] (MSC
>     service thread 1-2) JBAS015950:
>     WildFly 8.2.1.Final "Tweek" stopped in 415ms
>
>
>
>
>     --
>     View this message in context:
>     http://aerogear-users.1116366.n5.nabble.com/Unexpected-stops-for-Unified-push-server-tp496.html
>     Sent from the aerogear-users mailing list archive at Nabble.com.
>     _______________________________________________
>     Aerogear-users mailing list
>     [hidden email] </user/SendEmail.jtp?type=node&node=497&i=1>
>     https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
>
> _______________________________________________
> Aerogear-users mailing list
> [hidden email] </user/SendEmail.jtp?type=node&node=497&i=2>
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>
> ------------------------------------------------------------------------
> If you reply to this email, your message will be added to the 
> discussion below:
> http://aerogear-users.1116366.n5.nabble.com/Unexpected-stops-for-Unified-push-server-tp496p497.html 
>
> To unsubscribe from Unexpected stops for Unified push server, click 
> here 
> <http://aerogear-users.1116366.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=496&code=eXZlcy5uaWNvbGFzQGR5bmFtZWFzZS5jb218NDk2fDE4OTM0MjkzNDY=>.
> NAML 
> <http://aerogear-users.1116366.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> 
>





--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Unexpected-stops-for-Unified-push-server-tp496p498.html
Sent from the aerogear-users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160130/d2fc9409/attachment.html 

From daniel.orton at d2electronics.co.uk  Sat Jan 30 05:29:04 2016
From: daniel.orton at d2electronics.co.uk (Daniel Orton)
Date: Sat, 30 Jan 2016 03:29:04 -0700 (MST)
Subject: [Aerogear-users] Trouble sending Android Push Notifications
 [Solved]
In-Reply-To: <2E2AC2E8-DF8C-4587-A866-B6E5E262B88E@robertwillett.com>
References: <A496F5B4-A8E6-4B9D-8A77-C04D5F347C9F@robertwillett.com>
	<CADF=h2scz1H6mrrsCMpVg=BfDw+fUXYXTV-kLm6xySJZffMang@mail.gmail.com>
	<CAD_dpu1ypAaxzqMGjR5y-nZpTrsLU2d-4SGLNQjiH8x7V2RH5g@mail.gmail.com>
	<BA8854A1-072A-4B16-B524-3B7CEAB283F5@robertwillett.com>
	<CAD_dpu1Efe_fdj24sNo-rTAJS4Om7L-knmt3ZVY7WB4VTphSHw@mail.gmail.com>
	<D6F9E760-E031-4A7A-B277-B10DD17BB3E1@robertwillett.com>
	<7909D286-91DD-4612-BF23-7D703725519C@robertwillett.com>
	<CAD_dpu2pzWguAcJhNPFHJ75vhNmQ496H4BrtDeEiyoMp7i60Pg@mail.gmail.com>
	<2E2AC2E8-DF8C-4587-A866-B6E5E262B88E@robertwillett.com>
Message-ID: <1454149744455-499.post@n5.nabble.com>

Has this been resolved? I appear to be having the same issue even when
registering, deregistering and registering again I receive the same token in
UPS. Is this possibly linked to  AGDROID-486
<https://issues.jboss.org/browse/AGDROID-486>  ?



--
View this message in context: http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Trouble-sending-Android-Push-Notifications-tp295p499.html
Sent from the aerogear-users mailing list archive at Nabble.com.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160130/569bdf31/attachment.html 

From dpassos at redhat.com  Sat Jan 30 17:33:29 2016
From: dpassos at redhat.com (Daniel Passos)
Date: Sat, 30 Jan 2016 20:33:29 -0200
Subject: [Aerogear-users] Trouble sending Android Push Notifications
	[Solved]
In-Reply-To: <1454149744455-499.post@n5.nabble.com>
References: <A496F5B4-A8E6-4B9D-8A77-C04D5F347C9F@robertwillett.com>
	<CADF=h2scz1H6mrrsCMpVg=BfDw+fUXYXTV-kLm6xySJZffMang@mail.gmail.com>
	<CAD_dpu1ypAaxzqMGjR5y-nZpTrsLU2d-4SGLNQjiH8x7V2RH5g@mail.gmail.com>
	<BA8854A1-072A-4B16-B524-3B7CEAB283F5@robertwillett.com>
	<CAD_dpu1Efe_fdj24sNo-rTAJS4Om7L-knmt3ZVY7WB4VTphSHw@mail.gmail.com>
	<D6F9E760-E031-4A7A-B277-B10DD17BB3E1@robertwillett.com>
	<7909D286-91DD-4612-BF23-7D703725519C@robertwillett.com>
	<CAD_dpu2pzWguAcJhNPFHJ75vhNmQ496H4BrtDeEiyoMp7i60Pg@mail.gmail.com>
	<2E2AC2E8-DF8C-4587-A866-B6E5E262B88E@robertwillett.com>
	<1454149744455-499.post@n5.nabble.com>
Message-ID: <CADF=h2vYZagab-B9maHHa9CfxuLTBgWHPh9=jS6=O_6uQGWrDw@mail.gmail.com>

Daniel,

What aerogear-android-push version are you using?

On Sat, Jan 30, 2016 at 8:29 AM, Daniel Orton <
daniel.orton at d2electronics.co.uk> wrote:

> Has this been resolved? I appear to be having the same issue even when
> registering, deregistering and registering again I receive the same token
> in UPS. Is this possibly linked to AGDROID-486
> <https://issues.jboss.org/browse/AGDROID-486>?
> ------------------------------
> View this message in context: Re: [Aerogear-users] Trouble sending
> Android Push Notifications [Solved]
> <http://aerogear-users.1116366.n5.nabble.com/Aerogear-users-Trouble-sending-Android-Push-Notifications-tp295p499.html>
> Sent from the aerogear-users mailing list archive
> <http://aerogear-users.1116366.n5.nabble.com/> at Nabble.com.
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
-- Passos
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20160130/31d01bbf/attachment.html