From matzew at apache.org  Thu Mar  1 09:06:24 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 1 Mar 2018 15:06:24 +0100
Subject: [Aerogear-users] JIRA instances: One for the better (or one to rule
	them all)
Message-ID: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>

Hi folks!

shortly after AeroGear.org project was started, and different technologies
and scopes were added, we started to reflect that with multiple different
JIRA instances. For instance besides the canonical AEROGEAR instance we
have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
(AGPUSH)* or Cordova (AGCORDOVA), to name only a few.

I am proposing to retire all instances and start using only the AEROGEAR
instance.

In Push, we had similar discussion, we had different instances for
simplepush, ups and webpush; For sanity we ended up running all things in
AGPUSH, and using components and better version strings (e.g.
simplepush-1.0.0 or ups-1.2.4). And this works great

So, I think it does make sense to stop hammering new issues into all the
different "technology silos", like AGDROID or AGPUSH. Instead I really
think we should unify one JIRA instance, with proper components and much
better version strings, allowing us to really use one instance for all of
AeroGear.

Today, to me, it does look a bit that our multiple instances of JIRA can be
really done w/ one JIRA (and components/versions) instead - we don't really
have much more value w/ all the different instances.

I'd like to retire the new instances, in the near future, moving forward
with just one JIRA instance. At some point - later this year - we could
than try to delete the other redundant JIRA silos.

Before retiring the instances, we will review the existing backlogs and
port over valid tickets. So no *relevant* ticket will be lost, and outdated
tickets kinda gets cleaned up, doing this excercise :-)

Feedback, thoughts, tomatos ?

-Matthias


-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/fedc0839/attachment-0001.html 

From weil at redhat.com  Thu Mar  1 09:18:03 2018
From: weil at redhat.com (Wei Li)
Date: Thu, 1 Mar 2018 14:18:03 +0000
Subject: [Aerogear-users] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
Message-ID: <CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A@mail.gmail.com>

+1

On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> shortly after AeroGear.org project was started, and different technologies
> and scopes were added, we started to reflect that with multiple different
> JIRA instances. For instance besides the canonical AEROGEAR instance we
> have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
> (AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
>
> I am proposing to retire all instances and start using only the AEROGEAR
> instance.
>
> In Push, we had similar discussion, we had different instances for
> simplepush, ups and webpush; For sanity we ended up running all things in
> AGPUSH, and using components and better version strings (e.g.
> simplepush-1.0.0 or ups-1.2.4). And this works great
>
> So, I think it does make sense to stop hammering new issues into all the
> different "technology silos", like AGDROID or AGPUSH. Instead I really
> think we should unify one JIRA instance, with proper components and much
> better version strings, allowing us to really use one instance for all of
> AeroGear.
>
> Today, to me, it does look a bit that our multiple instances of JIRA can
> be really done w/ one JIRA (and components/versions) instead - we don't
> really have much more value w/ all the different instances.
>
> I'd like to retire the new instances, in the near future, moving forward
> with just one JIRA instance. At some point - later this year - we could
> than try to delete the other redundant JIRA silos.
>
> Before retiring the instances, we will review the existing backlogs and
> port over valid tickets. So no *relevant* ticket will be lost, and
> outdated tickets kinda gets cleaned up, doing this excercise :-)
>
> Feedback, thoughts, tomatos ?
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

WEI LI

SENIOR SOFTWARE ENGINEER

Red Hat Mobile <https://www.redhat.com/>

weil at redhat.com    M: +353862393272
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/8ef7787f/attachment.html 

From seykota at gmx.net  Fri Mar  2 10:19:27 2018
From: seykota at gmx.net (Christoph Kettler)
Date: Fri, 2 Mar 2018 08:19:27 -0700 (MST)
Subject: [Aerogear-users] Problems to deliver PushNotification to all
 configured variants
Message-ID: <1520003967901-0.post@n5.nabble.com>

Hello AG-Team,

we are currently confrontet with serious problems regarding the delivery of
push messages to variants/devices.

Our system is running Aerogear UnifiedPush Server V1.2.0 on a Wildfly
10.1.0.final.

We have currently 11 Variants in an Application, and are pushing against
this Application. According to the log file (see below), all variants shall
be processed by the server. However, this is not true.

The configuration for "App <-> PushServer (Variant)" and for "PushService
(Google FCM) <-> PushServer" ist valid for each. 
We are able to sent a PushNotification directly from the Firebase console to
the app, and also directly from the AeroGear UI using "Send Notification To
This App". The PushNotifications will always be delivered.

Here is a listing from the Logging. You can see in the first line that the
server prepare for 11 Variants, but only 6 are handled:

2018-02-02 12:27:32,862 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Preparing message delivery and
loading tokens for the ANDROID 3rd-party Push Network (for 11 variants)
// push for 11 variants, fits with the configuration in the application

2018-02-02 12:27:32,871 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-4
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 1/11

2018-02-02 12:27:32,871 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-4 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM topic: /topics/1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx

2018-02-02 12:27:32,879 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #1, containing 1
tokens, for android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-10
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 2/11

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #7, containing 25
tokens, for android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-10 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 25 registrationIDs

2018-02-02 12:27:32,915 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-14
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 3/11

2018-02-02 12:27:32,916 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-14 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 9 registrationIDs

2018-02-02 12:27:32,924 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #9, containing 9
tokens, for android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,929 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-12
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 4/11

2018-02-02 12:27:32,929 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-12 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 11 registrationIDs

2018-02-02 12:27:32,931 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #12, containing 11
tokens, for android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,939 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-9
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
//variant no. 5/11

2018-02-02 12:27:32,940 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-9 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 10 registrationIDs

2018-02-02 12:27:32,940 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #14, containing 10
tokens, for android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)

2018-02-02 12:27:32,945 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-2
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 6/11

2018-02-02 12:27:32,946 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-2 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 3 registrationIDs

2018-02-02 12:27:32,946 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #16, containing 3
tokens, for android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
// logging ends here


Any known issues on that? Or, is there an "upper limit" for variants within
an application which should not be exceeded and maybe it can be configurated
to scale upwards?

Thanks for any help and feedback.

Best regards,
Chris






--
Sent from: http://aerogear-users.1116366.n5.nabble.com/

From seykota at gmx.net  Fri Mar  2 10:23:08 2018
From: seykota at gmx.net (Christoph Kettler)
Date: Fri, 2 Mar 2018 08:23:08 -0700 (MST)
Subject: [Aerogear-users] Problems to deliver PushNotification to all
 configured variants
Message-ID: <1520004188485-0.post@n5.nabble.com>

Hello AG-Team,

we are currently confrontet with serious problems regarding the delivery of
push messages to variants/devices.

Our system is running Aerogear UnifiedPush Server V1.2.0 on a Wildfly
10.1.0.final.

We have currently 11 Variants in an Application, and are pushing against
this Application. According to the log file (see below), all variants shall
be processed by the server. However, this is not true.

The configuration for "App <-> PushServer (Variant)" and for "PushService
(Google FCM) <-> PushServer" ist valid for each. 
We are able to sent a PushNotification directly from the Firebase console to
the app, and also directly from the AeroGear UI using "Send Notification To
This App". The PushNotifications will always be delivered.

Here is a listing from the Logging. You can see in the first line that the
server prepare for 11 Variants, but only 6 are handled:

2018-02-02 12:27:32,862 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Preparing message delivery and
loading tokens for the ANDROID 3rd-party Push Network (for 11 variants)
// push for 11 variants, fits with the configuration in the application

2018-02-02 12:27:32,871 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-4
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 1/11

2018-02-02 12:27:32,871 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-4 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM topic: /topics/1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx

2018-02-02 12:27:32,879 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #1, containing 1
tokens, for android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-10
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 2/11

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #7, containing 25
tokens, for android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-10 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 25 registrationIDs

2018-02-02 12:27:32,915 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-14
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 3/11

2018-02-02 12:27:32,916 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-14 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 9 registrationIDs

2018-02-02 12:27:32,924 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #9, containing 9
tokens, for android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,929 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-12
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 4/11

2018-02-02 12:27:32,929 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-12 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 11 registrationIDs

2018-02-02 12:27:32,931 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #12, containing 11
tokens, for android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,939 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-9
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
//variant no. 5/11

2018-02-02 12:27:32,940 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-9 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 10 registrationIDs

2018-02-02 12:27:32,940 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #14, containing 10
tokens, for android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)

2018-02-02 12:27:32,945 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-2
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 6/11

2018-02-02 12:27:32,946 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-2 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 3 registrationIDs

2018-02-02 12:27:32,946 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #16, containing 3
tokens, for android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
// logging ends here


Any known issues on that? Or, is there an "upper limit" for variants within
an application which should not be exceeded and maybe it can be configurated
to scale upwards?

Thanks for any help and feedback.

Best regards,
Chris




--
Sent from: http://aerogear-users.1116366.n5.nabble.com/

From seykota at gmx.net  Fri Mar  2 10:25:18 2018
From: seykota at gmx.net (Christoph Kettler)
Date: Fri, 2 Mar 2018 08:25:18 -0700 (MST)
Subject: [Aerogear-users] Problems to deliver PushNotification to all
 configured variants
Message-ID: <1520004318317-0.post@n5.nabble.com>

Hello AG-Team,

we are currently confrontet with serious problems regarding the delivery of
push messages to variants/devices.

Our system is running Aerogear UnifiedPush Server V1.2.0 on a Wildfly
10.1.0.final.

We have currently 11 Variants in an Application, and are pushing against
this Application. According to the log file (see below), all variants shall
be processed by the server. However, this is not true.

The configuration for "App <-> PushServer (Variant)" and for "PushService
(Google FCM) <-> PushServer" ist valid for each. 
We are able to sent a PushNotification directly from the Firebase console to
the app, and also directly from the AeroGear UI using "Send Notification To
This App". The PushNotifications will always be delivered.

Here is a listing from the Logging. You can see in the first line that the
server prepare for 11 Variants, but only 6 are handled:

2018-02-02 12:27:32,862 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Preparing message delivery and
loading tokens for the ANDROID 3rd-party Push Network (for 11 variants)
// push for 11 variants, fits with the configuration in the application

2018-02-02 12:27:32,871 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-4
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 1/11

2018-02-02 12:27:32,871 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-4 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM topic: /topics/1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx

2018-02-02 12:27:32,879 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #1, containing 1
tokens, for android variant (1a954f3a-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-10
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 2/11

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #7, containing 25
tokens, for android variant (2bced2f9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,898 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-10 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 25 registrationIDs

2018-02-02 12:27:32,915 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-14
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 3/11

2018-02-02 12:27:32,916 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-14 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 9 registrationIDs

2018-02-02 12:27:32,924 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #9, containing 9
tokens, for android variant (3c4dc8c3-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,929 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-12
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 4/11

2018-02-02 12:27:32,929 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-12 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 11 registrationIDs

2018-02-02 12:27:32,931 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #12, containing 11
tokens, for android variant (4d1799d9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)

2018-02-02 12:27:32,939 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-9
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)
//variant no. 5/11

2018-02-02 12:27:32,940 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-9 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 10 registrationIDs

2018-02-02 12:27:32,940 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #14, containing 10
tokens, for android variant (5e2ef234-xxxx-xxxx-xxxx-xxxXXXxxx)

2018-02-02 12:27:32,945 INFO 
[org.jboss.aerogear.unifiedpush.message.NotificationDispatcher] (Thread-2
(ActiveMQ-client-global-threads-1362505470)) Received UnifiedPushMessage
from JMS queue, will now trigger the Push Notification delivery for the
android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
//variant no. 6/11

2018-02-02 12:27:32,946 INFO 
[org.jboss.aerogear.unifiedpush.message.sender.FCMPushNotificationSender]
(Thread-2 (ActiveMQ-client-global-threads-1362505470)) Sent push
notification to FCM Server for 3 registrationIDs

2018-02-02 12:27:32,946 INFO 
[org.jboss.aerogear.unifiedpush.message.token.TokenLoader] (Thread-5
(ActiveMQ-client-global-threads-1362505470)) Loaded batch #16, containing 3
tokens, for android variant (6fe1c2b9-xxxx-xxxx-xxxx-xxxxXXXXxxxx)
// logging ends here


Any known issues on that? Or, is there an "upper limit" for variants within
an application which should not be exceeded and maybe it can be configurated
to scale upwards?

Thanks for any help and feedback.

Best regards,
Chris




--
Sent from: http://aerogear-users.1116366.n5.nabble.com/

From rbaumgar at redhat.com  Wed Mar 21 11:47:00 2018
From: rbaumgar at redhat.com (Robert Baumgartner)
Date: Wed, 21 Mar 2018 16:47:00 +0100
Subject: [Aerogear-users] Aearogear with Android SDK on OpenShift: Default
	FirebaseApp is not initialized
Message-ID: <CAKdJ40S8QtHvwjsFUjAjYHEiSsYpCKEhdWVdgQarcTvG+1qGxw@mail.gmail.com>

Hi Gurus,

I tried to use AeroGear and run into a little problem...

I installes Aerogear on OpenShift/Minishift incl Kerberos, like
https://github.com/aerogear/aerogear-unifiedpush-server/

After that I used the guide at:
https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/

Then I got a complier error when I tried to run the  PushApplication

Error:(25, 23) error: TAG has private access in FragmentActivity

I tried to fixed this in
MainActivity.java by adding a
    private static final String TAG = MainActivity.class.getSimpleName();


So I got the following error at application runtime:
W/System: ClassLoader referenced unknown path:
/data/app/com.push.pushapplication-1/lib/arm64
I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
I/InstantRun: starting instant run server: is main process
W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
android.support.graphics.drawable.VectorDrawableCompat.updat
eTintFilter(android.graphics.PorterDuffColorFilter,
android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would
have incorrectly overridden the package-private method in
android.graphics.drawable.Drawable
E/MainActivity: *Default FirebaseApp is not initialized in this process
com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.*
                java.lang.IllegalStateException: Default FirebaseApp is not
initialized in this process com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.
                    at com.google.firebase.FirebaseApp.getInstance(Unknown
Source)
                    at com.google.firebase.iid.Fireba
seInstanceId.getInstance(Unknown Source)
                    at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:
100)
                    at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:
96)
                    at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
earFCMPushRegistrar.java:145)
                    at org.jboss.aerogear.android.uni
fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
earFCMPushRegistrar.java:135)
                    at android.os.AsyncTask$2.call(AsyncTask.java:305)
                    at java.util.concurrent.FutureTas
k.run(FutureTask.java:237)
                    at android.os.AsyncTask$SerialExe
cutor$1.run(AsyncTask.java:243)
                    at java.util.concurrent.ThreadPoo
lExecutor.runWorker(ThreadPoolExecutor.java:1133)
                    at java.util.concurrent.ThreadPoo
lExecutor$Worker.run(ThreadPoolExecutor.java:607)
                    at java.lang.Thread.run(Thread.java:761)

I could not find any workaroud. Any tip/solution wolcome?

Lg Robert
Mit freundlichen Gr??en / Kind regards


Robert Baumgartner

Senior Solution Architect Middleware

Red Hat Austria GmbH <https://www.redhat.com>

Millenniumtower 24.Stock

Handelskai 94-96

A-1200 Wien

robert.baumgartner at redhat.com    M: +43-660-5913883
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180321/0a649bc2/attachment.html 

From matzew at apache.org  Thu Mar 22 08:17:43 2018
From: matzew at apache.org (Matthias Wessendorf)
Date: Thu, 22 Mar 2018 13:17:43 +0100
Subject: [Aerogear-users] Aearogear with Android SDK on OpenShift:
 Default FirebaseApp is not initialized
In-Reply-To: <CAKdJ40S8QtHvwjsFUjAjYHEiSsYpCKEhdWVdgQarcTvG+1qGxw@mail.gmail.com>
References: <CAKdJ40S8QtHvwjsFUjAjYHEiSsYpCKEhdWVdgQarcTvG+1qGxw@mail.gmail.com>
Message-ID: <CAAg5f2SxdHxEc8poui2__4-riD4DNTBRoC7R+kDPbSFH2fMBig@mail.gmail.com>

Hey Robert,

thanks for reacing out - I hope that passos or summers can be helpful with
your issue here

On Wed, Mar 21, 2018 at 4:47 PM, Robert Baumgartner <rbaumgar at redhat.com>
wrote:

> Hi Gurus,
>
> I tried to use AeroGear and run into a little problem...
>
> I installes Aerogear on OpenShift/Minishift incl Kerberos, like
> https://github.com/aerogear/aerogear-unifiedpush-server/
>
> After that I used the guide at:
> https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/
>
> Then I got a complier error when I tried to run the  PushApplication
>
> Error:(25, 23) error: TAG has private access in FragmentActivity
>
> I tried to fixed this in
> MainActivity.java by adding a
>     private static final String TAG = MainActivity.class.getSimpleName();
>
>
> So I got the following error at application runtime:
> W/System: ClassLoader referenced unknown path:
> /data/app/com.push.pushapplication-1/lib/arm64
> I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
> I/InstantRun: starting instant run server: is main process
> W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
> android.support.graphics.drawable.VectorDrawableCompat.updat
> eTintFilter(android.graphics.PorterDuffColorFilter,
> android.content.res.ColorStateList, android.graphics.PorterDuff$Mode)
> would have incorrectly overridden the package-private method in
> android.graphics.drawable.Drawable
> E/MainActivity: *Default FirebaseApp is not initialized in this process
> com.push.pushapplication. Make sure to call
> FirebaseApp.initializeApp(Context) first.*
>                 java.lang.IllegalStateException: Default FirebaseApp is
> not initialized in this process com.push.pushapplication. Make sure to call
> FirebaseApp.initializeApp(Context) first.
>                     at com.google.firebase.FirebaseApp.getInstance(Unknown
> Source)
>                     at com.google.firebase.iid.Fireba
> seInstanceId.getInstance(Unknown Source)
>                     at org.jboss.aerogear.android.uni
> fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushR
> egistrar.java:100)
>                     at org.jboss.aerogear.android.uni
> fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushR
> egistrar.java:96)
>                     at org.jboss.aerogear.android.uni
> fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
> earFCMPushRegistrar.java:145)
>                     at org.jboss.aerogear.android.uni
> fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
> earFCMPushRegistrar.java:135)
>                     at android.os.AsyncTask$2.call(AsyncTask.java:305)
>                     at java.util.concurrent.FutureTas
> k.run(FutureTask.java:237)
>                     at android.os.AsyncTask$SerialExe
> cutor$1.run(AsyncTask.java:243)
>                     at java.util.concurrent.ThreadPoo
> lExecutor.runWorker(ThreadPoolExecutor.java:1133)
>                     at java.util.concurrent.ThreadPoo
> lExecutor$Worker.run(ThreadPoolExecutor.java:607)
>                     at java.lang.Thread.run(Thread.java:761)
>
> I could not find any workaroud. Any tip/solution wolcome?
>
> Lg Robert
> Mit freundlichen Gr??en / Kind regards
>
>
> Robert Baumgartner
>
> Senior Solution Architect Middleware
>
> Red Hat Austria GmbH <https://www.redhat.com>
>
> Millenniumtower 24.Stock
>
> Handelskai 94-96
>
> A-1200 Wien
>
> robert.baumgartner at redhat.com    M: +43-660-5913883
> <https://red.ht/sig>
>
>
> _______________________________________________
> Aerogear-users mailing list
> Aerogear-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-users
>
>


-- 
Matthias Wessendorf

github: https://github.com/matzew
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180322/5eb9b12f/attachment-0001.html 

From dpassos at redhat.com  Thu Mar 22 10:17:29 2018
From: dpassos at redhat.com (Daniel Passos)
Date: Thu, 22 Mar 2018 11:17:29 -0300
Subject: [Aerogear-users] Aearogear with Android SDK on OpenShift:
 Default FirebaseApp is not initialized
In-Reply-To: <CAAg5f2SxdHxEc8poui2__4-riD4DNTBRoC7R+kDPbSFH2fMBig@mail.gmail.com>
References: <CAKdJ40S8QtHvwjsFUjAjYHEiSsYpCKEhdWVdgQarcTvG+1qGxw@mail.gmail.com>
	<CAAg5f2SxdHxEc8poui2__4-riD4DNTBRoC7R+kDPbSFH2fMBig@mail.gmail.com>
Message-ID: <CADF=h2sN2HiYAgz8FWTQdrhct9=5b_zVx+i8_Pi-iRQEvd1tzQ@mail.gmail.com>

Hey Robert,

FirebaseApp.initializeApp(Context) means you have not configured Firebase
correctly.

Can you check if you have added this:

https://github.com/aerogear/aerogear-android-cookbook/blob/master/HelloPush/build.gradle#L9
?

On Thu, Mar 22, 2018 at 9:17 AM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hey Robert,
>
> thanks for reacing out - I hope that passos or summers can be helpful with
> your issue here
>
> On Wed, Mar 21, 2018 at 4:47 PM, Robert Baumgartner <rbaumgar at redhat.com>
> wrote:
>
>> Hi Gurus,
>>
>> I tried to use AeroGear and run into a little problem...
>>
>> I installes Aerogear on OpenShift/Minishift incl Kerberos, like
>> https://github.com/aerogear/aerogear-unifiedpush-server/
>>
>> After that I used the guide at:
>> https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/
>>
>> Then I got a complier error when I tried to run the  PushApplication
>>
>> Error:(25, 23) error: TAG has private access in FragmentActivity
>>
>> I tried to fixed this in
>> MainActivity.java by adding a
>>     private static final String TAG = MainActivity.class.getSimpleName();
>>
>>
>> So I got the following error at application runtime:
>> W/System: ClassLoader referenced unknown path:
>> /data/app/com.push.pushapplication-1/lib/arm64
>> I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
>> I/InstantRun: starting instant run server: is main process
>> W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
>> android.support.graphics.drawable.VectorDrawableCompat.updat
>> eTintFilter(android.graphics.PorterDuffColorFilter,
>> android.content.res.ColorStateList, android.graphics.PorterDuff$Mode)
>> would have incorrectly overridden the package-private method in
>> android.graphics.drawable.Drawable
>> E/MainActivity: *Default FirebaseApp is not initialized in this process
>> com.push.pushapplication. Make sure to call
>> FirebaseApp.initializeApp(Context) first.*
>>                 java.lang.IllegalStateException: Default FirebaseApp is
>> not initialized in this process com.push.pushapplication. Make sure to call
>> FirebaseApp.initializeApp(Context) first.
>>                     at com.google.firebase.FirebaseApp.getInstance(Unknown
>> Source)
>>                     at com.google.firebase.iid.Fireba
>> seInstanceId.getInstance(Unknown Source)
>>                     at org.jboss.aerogear.android.uni
>> fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushR
>> egistrar.java:100)
>>                     at org.jboss.aerogear.android.uni
>> fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushR
>> egistrar.java:96)
>>                     at org.jboss.aerogear.android.uni
>> fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
>> earFCMPushRegistrar.java:145)
>>                     at org.jboss.aerogear.android.uni
>> fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
>> earFCMPushRegistrar.java:135)
>>                     at android.os.AsyncTask$2.call(AsyncTask.java:305)
>>                     at java.util.concurrent.FutureTas
>> k.run(FutureTask.java:237)
>>                     at android.os.AsyncTask$SerialExe
>> cutor$1.run(AsyncTask.java:243)
>>                     at java.util.concurrent.ThreadPoo
>> lExecutor.runWorker(ThreadPoolExecutor.java:1133)
>>                     at java.util.concurrent.ThreadPoo
>> lExecutor$Worker.run(ThreadPoolExecutor.java:607)
>>                     at java.lang.Thread.run(Thread.java:761)
>>
>> I could not find any workaroud. Any tip/solution wolcome?
>>
>> Lg Robert
>> Mit freundlichen Gr??en / Kind regards
>>
>>
>> Robert Baumgartner
>>
>> Senior Solution Architect Middleware
>>
>> Red Hat Austria GmbH <https://www.redhat.com>
>>
>> Millenniumtower 24.Stock
>>
>> Handelskai 94-96
>> <https://maps.google.com/?q=Handelskai+94-96&entry=gmail&source=g>
>>
>> A-1200 Wien
>>
>> robert.baumgartner at redhat.com    M: +43-660-5913883
>> <https://red.ht/sig>
>>
>>
>> _______________________________________________
>> Aerogear-users mailing list
>> Aerogear-users at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>
>>
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>



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

From supittma at redhat.com  Thu Mar 22 10:53:30 2018
From: supittma at redhat.com (Summers Pittman)
Date: Thu, 22 Mar 2018 10:53:30 -0400
Subject: [Aerogear-users] Aearogear with Android SDK on OpenShift:
 Default FirebaseApp is not initialized
In-Reply-To: <CADF=h2sN2HiYAgz8FWTQdrhct9=5b_zVx+i8_Pi-iRQEvd1tzQ@mail.gmail.com>
References: <CAKdJ40S8QtHvwjsFUjAjYHEiSsYpCKEhdWVdgQarcTvG+1qGxw@mail.gmail.com>
	<CAAg5f2SxdHxEc8poui2__4-riD4DNTBRoC7R+kDPbSFH2fMBig@mail.gmail.com>
	<CADF=h2sN2HiYAgz8FWTQdrhct9=5b_zVx+i8_Pi-iRQEvd1tzQ@mail.gmail.com>
Message-ID: <CAEQz2Cthorgq-d-2A6HSG30wkBidHX9kKXPCRbA_bC74DFVZtg@mail.gmail.com>

Robert,

Can you share your projects on github?  Also are you using fhcap,
mobile-core, or stanalone UPS?

On Thu, Mar 22, 2018 at 10:17 AM, Daniel Passos <dpassos at redhat.com> wrote:

> Hey Robert,
>
> FirebaseApp.initializeApp(Context) means you have not configured Firebase
> correctly.
>
> Can you check if you have added this:
>
> https://github.com/aerogear/aerogear-android-cookbook/
> blob/master/HelloPush/build.gradle#L9
> ?
>
> On Thu, Mar 22, 2018 at 9:17 AM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hey Robert,
>>
>> thanks for reacing out - I hope that passos or summers can be helpful
>> with your issue here
>>
>> On Wed, Mar 21, 2018 at 4:47 PM, Robert Baumgartner <rbaumgar at redhat.com>
>> wrote:
>>
>>> Hi Gurus,
>>>
>>> I tried to use AeroGear and run into a little problem...
>>>
>>> I installes Aerogear on OpenShift/Minishift incl Kerberos, like
>>> https://github.com/aerogear/aerogear-unifiedpush-server/
>>>
>>> After that I used the guide at:
>>> https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/
>>>
>>> Then I got a complier error when I tried to run the  PushApplication
>>>
>>> Error:(25, 23) error: TAG has private access in FragmentActivity
>>>
>>> I tried to fixed this in
>>> MainActivity.java by adding a
>>>     private static final String TAG = MainActivity.class.getSimpleNa
>>> me();
>>>
>>>
>>> So I got the following error at application runtime:
>>> W/System: ClassLoader referenced unknown path:
>>> /data/app/com.push.pushapplication-1/lib/arm64
>>> I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
>>> I/InstantRun: starting instant run server: is main process
>>> W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
>>> android.support.graphics.drawable.VectorDrawableCompat.updat
>>> eTintFilter(android.graphics.PorterDuffColorFilter,
>>> android.content.res.ColorStateList, android.graphics.PorterDuff$Mode)
>>> would have incorrectly overridden the package-private method in
>>> android.graphics.drawable.Drawable
>>> E/MainActivity: *Default FirebaseApp is not initialized in this process
>>> com.push.pushapplication. Make sure to call
>>> FirebaseApp.initializeApp(Context) first.*
>>>                 java.lang.IllegalStateException: Default FirebaseApp is
>>> not initialized in this process com.push.pushapplication. Make sure to call
>>> FirebaseApp.initializeApp(Context) first.
>>>                     at com.google.firebase.FirebaseApp.getInstance(Unknown
>>> Source)
>>>                     at com.google.firebase.iid.Fireba
>>> seInstanceId.getInstance(Unknown Source)
>>>                     at org.jboss.aerogear.android.uni
>>> fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushR
>>> egistrar.java:100)
>>>                     at org.jboss.aerogear.android.uni
>>> fiedpush.fcm.AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushR
>>> egistrar.java:96)
>>>                     at org.jboss.aerogear.android.uni
>>> fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
>>> earFCMPushRegistrar.java:145)
>>>                     at org.jboss.aerogear.android.uni
>>> fiedpush.fcm.AeroGearFCMPushRegistrar$4.doInBackground(AeroG
>>> earFCMPushRegistrar.java:135)
>>>                     at android.os.AsyncTask$2.call(AsyncTask.java:305)
>>>                     at java.util.concurrent.FutureTas
>>> k.run(FutureTask.java:237)
>>>                     at android.os.AsyncTask$SerialExe
>>> cutor$1.run(AsyncTask.java:243)
>>>                     at java.util.concurrent.ThreadPoo
>>> lExecutor.runWorker(ThreadPoolExecutor.java:1133)
>>>                     at java.util.concurrent.ThreadPoo
>>> lExecutor$Worker.run(ThreadPoolExecutor.java:607)
>>>                     at java.lang.Thread.run(Thread.java:761)
>>>
>>> I could not find any workaroud. Any tip/solution wolcome?
>>>
>>> Lg Robert
>>> Mit freundlichen Gr??en / Kind regards
>>>
>>>
>>> Robert Baumgartner
>>>
>>> Senior Solution Architect Middleware
>>>
>>> Red Hat Austria GmbH <https://www.redhat.com>
>>>
>>> Millenniumtower 24.Stock
>>>
>>> Handelskai 94-96
>>> <https://maps.google.com/?q=Handelskai+94-96&entry=gmail&source=g>
>>>
>>> A-1200 Wien
>>>
>>> robert.baumgartner at redhat.com    M: +43-660-5913883
>>> <https://red.ht/sig>
>>>
>>>
>>> _______________________________________________
>>> Aerogear-users mailing list
>>> Aerogear-users at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-users
>>>
>>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> -- Passos
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180322/f5d16e19/attachment-0001.html 

From dara.hayes at redhat.com  Thu Mar  1 10:13:59 2018
From: dara.hayes at redhat.com (Dara Hayes)
Date: Thu, 01 Mar 2018 15:13:59 -0000
Subject: [Aerogear-users] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
Message-ID: <CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV=SsWhpoA@mail.gmail.com>

Seems like a no brainer to me. +1

On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> shortly after AeroGear.org project was started, and different technologies
> and scopes were added, we started to reflect that with multiple different
> JIRA instances. For instance besides the canonical AEROGEAR instance we
> have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
> (AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
>
> I am proposing to retire all instances and start using only the AEROGEAR
> instance.
>
> In Push, we had similar discussion, we had different instances for
> simplepush, ups and webpush; For sanity we ended up running all things in
> AGPUSH, and using components and better version strings (e.g.
> simplepush-1.0.0 or ups-1.2.4). And this works great
>
> So, I think it does make sense to stop hammering new issues into all the
> different "technology silos", like AGDROID or AGPUSH. Instead I really
> think we should unify one JIRA instance, with proper components and much
> better version strings, allowing us to really use one instance for all of
> AeroGear.
>
> Today, to me, it does look a bit that our multiple instances of JIRA can
> be really done w/ one JIRA (and components/versions) instead - we don't
> really have much more value w/ all the different instances.
>
> I'd like to retire the new instances, in the near future, moving forward
> with just one JIRA instance. At some point - later this year - we could
> than try to delete the other redundant JIRA silos.
>
> Before retiring the instances, we will review the existing backlogs and
> port over valid tickets. So no *relevant* ticket will be lost, and
> outdated tickets kinda gets cleaned up, doing this excercise :-)
>
> Feedback, thoughts, tomatos ?
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 

Dara Hayes

Associate software engineer
<https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/5db49aa4/attachment-0001.html 

From jfrizell at redhat.com  Thu Mar  1 10:17:33 2018
From: jfrizell at redhat.com (John Frizelle)
Date: Thu, 01 Mar 2018 15:17:33 -0000
Subject: [Aerogear-users] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV=SsWhpoA@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
	<CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV=SsWhpoA@mail.gmail.com>
Message-ID: <CAJFhnM7vnXVyH6DQWPZOht_7LZedPjvNYW3Y_v8wgcve=iHpow@mail.gmail.com>

HUGE +1 from me.

--
John Frizelle
Chief Architect, Red Hat Mobile
Consulting Engineer

mobile: *+353 87 290 1644 <//+353872901644>*
twitter:* @johnfriz*
skype: *john_frizelle*
mail: *jfrizell at redhat.com <jfrizell at redhat.com>*




On 1 March 2018 at 15:13, Dara Hayes <dara.hayes at redhat.com> wrote:

> Seems like a no brainer to me. +1
>
> On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi folks!
>>
>> shortly after AeroGear.org project was started, and different
>> technologies and scopes were added, we started to reflect that with
>> multiple different JIRA instances. For instance besides the canonical
>> AEROGEAR instance we have a bunch of them for iOS (AGIOS), Android
>> (AGDROID), All things Push (AGPUSH)* or Cordova (AGCORDOVA), to name only a
>> few.
>>
>> I am proposing to retire all instances and start using only the AEROGEAR
>> instance.
>>
>> In Push, we had similar discussion, we had different instances for
>> simplepush, ups and webpush; For sanity we ended up running all things in
>> AGPUSH, and using components and better version strings (e.g.
>> simplepush-1.0.0 or ups-1.2.4). And this works great
>>
>> So, I think it does make sense to stop hammering new issues into all the
>> different "technology silos", like AGDROID or AGPUSH. Instead I really
>> think we should unify one JIRA instance, with proper components and much
>> better version strings, allowing us to really use one instance for all of
>> AeroGear.
>>
>> Today, to me, it does look a bit that our multiple instances of JIRA can
>> be really done w/ one JIRA (and components/versions) instead - we don't
>> really have much more value w/ all the different instances.
>>
>> I'd like to retire the new instances, in the near future, moving forward
>> with just one JIRA instance. At some point - later this year - we could
>> than try to delete the other redundant JIRA silos.
>>
>> Before retiring the instances, we will review the existing backlogs and
>> port over valid tickets. So no *relevant* ticket will be lost, and
>> outdated tickets kinda gets cleaned up, doing this excercise :-)
>>
>> Feedback, thoughts, tomatos ?
>>
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_
>> mup3OOTF34NiX8Wzw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> Dara Hayes
>
> Associate software engineer
> <https://redhat.com> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV%3DSsWhpoA%
> 40mail.gmail.com
> <https://groups.google.com/d/msgid/aerogear/CABkcJC3zUncjSUUBidJsSh4K_Ezp98Ng50wDu27-uV%3DSsWhpoA%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/03a263fa/attachment-0001.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: logo.png
Type: image/png
Size: 11472 bytes
Desc: not available
Url : http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/03a263fa/attachment-0001.png 

From wtrocki at redhat.com  Thu Mar  1 09:49:40 2018
From: wtrocki at redhat.com (Wojciech Trocki)
Date: Thu, 01 Mar 2018 14:49:40 -0000
Subject: [Aerogear-users] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
	<CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A@mail.gmail.com>
Message-ID: <CAO0+n+qN+CDER+us_rcb=+TjZV0Fv_JLF8gX_bQEmqujn5wDNw@mail.gmail.com>

Unification will be awesome.
I have logged issues on the wrong project so many times.
It will help also with new platforms like ReactNative - we currently link
that to JS project, which is not accurate.

On Thu, Mar 1, 2018 at 2:18 PM, Wei Li <weil at redhat.com> wrote:

> +1
>
> On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
> wrote:
>
>> Hi folks!
>>
>> shortly after AeroGear.org project was started, and different
>> technologies and scopes were added, we started to reflect that with
>> multiple different JIRA instances. For instance besides the canonical
>> AEROGEAR instance we have a bunch of them for iOS (AGIOS), Android
>> (AGDROID), All things Push (AGPUSH)* or Cordova (AGCORDOVA), to name only a
>> few.
>>
>> I am proposing to retire all instances and start using only the AEROGEAR
>> instance.
>>
>> In Push, we had similar discussion, we had different instances for
>> simplepush, ups and webpush; For sanity we ended up running all things in
>> AGPUSH, and using components and better version strings (e.g.
>> simplepush-1.0.0 or ups-1.2.4). And this works great
>>
>> So, I think it does make sense to stop hammering new issues into all the
>> different "technology silos", like AGDROID or AGPUSH. Instead I really
>> think we should unify one JIRA instance, with proper components and much
>> better version strings, allowing us to really use one instance for all of
>> AeroGear.
>>
>> Today, to me, it does look a bit that our multiple instances of JIRA can
>> be really done w/ one JIRA (and components/versions) instead - we don't
>> really have much more value w/ all the different instances.
>>
>> I'd like to retire the new instances, in the near future, moving forward
>> with just one JIRA instance. At some point - later this year - we could
>> than try to delete the other redundant JIRA silos.
>>
>> Before retiring the instances, we will review the existing backlogs and
>> port over valid tickets. So no *relevant* ticket will be lost, and
>> outdated tickets kinda gets cleaned up, doing this excercise :-)
>>
>> Feedback, thoughts, tomatos ?
>>
>> -Matthias
>>
>>
>> --
>> Matthias Wessendorf
>>
>> github: https://github.com/matzew
>> twitter: http://twitter.com/mwessendorf
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Aerogear" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to aerogear+unsubscribe at googlegroups.com.
>> To post to this group, send email to aerogear at googlegroups.com.
>> To view this discussion on the web visit https://groups.google.com/d/ms
>> gid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_
>> mup3OOTF34NiX8Wzw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
>
> WEI LI
>
> SENIOR SOFTWARE ENGINEER
>
> Red Hat Mobile <https://www.redhat.com/>
>
> weil at redhat.com    M: +353862393272
> <https://red.ht/sig>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAHmyU2pF9yQ595H069h51bjNMwaHM8D4f7U_UdTJ953pdAX50A%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 

WOJCIECH TROCKI

Red Hat Mobile <https://www.redhat.com/>

IM: wtrocki
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/4a7e4836/attachment-0001.html 

From jmadigan at redhat.com  Thu Mar  1 10:55:31 2018
From: jmadigan at redhat.com (Jason Madigan)
Date: Thu, 01 Mar 2018 15:55:31 -0000
Subject: [Aerogear-users] JIRA instances: One for the better (or one to
	rule them all)
In-Reply-To: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
References: <CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw@mail.gmail.com>
Message-ID: <CAKPPhh9-cJX3dsObYzUKT4m4ZX2P9N74+ikoKv++pbdU1jyqOQ@mail.gmail.com>

+1

On Thu, Mar 1, 2018 at 2:06 PM, Matthias Wessendorf <matzew at apache.org>
wrote:

> Hi folks!
>
> shortly after AeroGear.org project was started, and different technologies
> and scopes were added, we started to reflect that with multiple different
> JIRA instances. For instance besides the canonical AEROGEAR instance we
> have a bunch of them for iOS (AGIOS), Android (AGDROID), All things Push
> (AGPUSH)* or Cordova (AGCORDOVA), to name only a few.
>
> I am proposing to retire all instances and start using only the AEROGEAR
> instance.
>
> In Push, we had similar discussion, we had different instances for
> simplepush, ups and webpush; For sanity we ended up running all things in
> AGPUSH, and using components and better version strings (e.g.
> simplepush-1.0.0 or ups-1.2.4). And this works great
>
> So, I think it does make sense to stop hammering new issues into all the
> different "technology silos", like AGDROID or AGPUSH. Instead I really
> think we should unify one JIRA instance, with proper components and much
> better version strings, allowing us to really use one instance for all of
> AeroGear.
>
> Today, to me, it does look a bit that our multiple instances of JIRA can
> be really done w/ one JIRA (and components/versions) instead - we don't
> really have much more value w/ all the different instances.
>
> I'd like to retire the new instances, in the near future, moving forward
> with just one JIRA instance. At some point - later this year - we could
> than try to delete the other redundant JIRA silos.
>
> Before retiring the instances, we will review the existing backlogs and
> port over valid tickets. So no *relevant* ticket will be lost, and
> outdated tickets kinda gets cleaned up, doing this excercise :-)
>
> Feedback, thoughts, tomatos ?
>
> -Matthias
>
>
> --
> Matthias Wessendorf
>
> github: https://github.com/matzew
> twitter: http://twitter.com/mwessendorf
>
> --
> You received this message because you are subscribed to the Google Groups
> "Aerogear" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to aerogear+unsubscribe at googlegroups.com.
> To post to this group, send email to aerogear at googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.
> gmail.com
> <https://groups.google.com/d/msgid/aerogear/CAAg5f2Tj0zA3KxBfMcY6DZsUYyrS4WtD_mup3OOTF34NiX8Wzw%40mail.gmail.com?utm_medium=email&utm_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Jason Madigan
Engineering Manager, Red Hat Mobile
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180301/007537b4/attachment-0001.html 

From rbaumgar at redhat.com  Tue Mar 20 19:26:57 2018
From: rbaumgar at redhat.com (Robert Baumgartner)
Date: Tue, 20 Mar 2018 23:26:57 -0000
Subject: [Aerogear-users] Aearogear with Android SDk on OpenShift
Message-ID: <CAKdJ40R4srJwCDMXX8HfGUoNEn-tbrRH4pcOeOtWGovDjJ1fQQ@mail.gmail.com>

Hi Gurus,

I tried to use AeroGear and run into a little problem...

I installes Aerogear on OpenShift/Minishift incl Kerberos, like
https://github.com/aerogear/aerogear-unifiedpush-server/

After that I used the guide at:
https://aerogear.org/docs/unifiedpush/aerogear-push-android/guides/

Then I got a complier error when I tried to run the  PushApplication

Error:(25, 23) error: TAG has private access in FragmentActivity

I tried to fixed this in
MainActivity.java by adding a
    private static final String TAG = MainActivity.class.getSimpleName();


So I got the following error at application runtime:
W/System: ClassLoader referenced unknown path: /data/app/com.push.
pushapplication-1/lib/arm64
I/FirebaseInitProvider: FirebaseApp initialization unsuccessful
I/InstantRun: starting instant run server: is main process
W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter
android.support.graphics.drawable.VectorDrawableCompat.
updateTintFilter(android.graphics.PorterDuffColorFilter,
android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would
have incorrectly overridden the package-private method in
android.graphics.drawable.Drawable
E/MainActivity: *Default FirebaseApp is not initialized in this process
com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.*
                java.lang.IllegalStateException: Default FirebaseApp is not
initialized in this process com.push.pushapplication. Make sure to call
FirebaseApp.initializeApp(Context) first.
                    at com.google.firebase.FirebaseApp.getInstance(Unknown
Source)
                    at
com.google.firebase.iid.FirebaseInstanceId.getInstance(Unknown
Source)
                    at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:100)
                    at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$2.get(AeroGearFCMPushRegistrar.java:96)
                    at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$4.doInBackground(AeroGearFCMPushRegistrar.java:145)
                    at org.jboss.aerogear.android.unifiedpush.fcm.
AeroGearFCMPushRegistrar$4.doInBackground(AeroGearFCMPushRegistrar.java:135)
                    at android.os.AsyncTask$2.call(AsyncTask.java:305)
                    at java.util.concurrent.FutureTask.run(FutureTask.
java:237)
                    at android.os.AsyncTask$SerialExecutor$1.run(
AsyncTask.java:243)
                    at java.util.concurrent.ThreadPoolExecutor.runWorker(
ThreadPoolExecutor.java:1133)
                    at java.util.concurrent.ThreadPoolExecutor$Worker.run(
ThreadPoolExecutor.java:607)
                    at java.lang.Thread.run(Thread.java:761)

I could not find any workaroud. Any tip/solution wolcome?

Lg Robert
Kind regards


Robert Baumgartner

Senior Solution Architect Middleware

Red Hat Austria GmbH <https://www.redhat.com>

Millenniumtower 24.Stock

Handelskai 94-96

A-1200 Wien

robert.baumgartner at redhat.com    M: +43-660-5913883
<https://red.ht/sig>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-users/attachments/20180320/0e2010dd/attachment.html