I've setup a new Nabble forum as an archive and forum for aerogears-users,
as it may be sometimes more convenient for searching & posting.
You will find it here: http://aerogear-users.1116366.n5.nabble.com/
Good morning, I was reviewing our SDK for iOS and I have few questions:
1. For example at Shoot app. Why our users have to configure to insert
the app ID at Shoot-Info.plist and also insert the same app ID at
ViewController? I was just wondering that once the app ID is informed,
you don't need to inform it again.
2. We have a note:
"Because this demo securely stores OAuth2 tokens in your iOS keychain,
we chosen to use WhenPasscodeSet policy as a result to run this app you
need to have your passcode set"
I think that's amazing, but at the same time we instruct our devs, to
insert the client secret hard coded into the app. Something like:
let facebookConfig = FacebookConfig(
Doing the reverse engineering of the app, would permit me to get the
secret and mimic your FB app.
So I would like to remove the need to input the same information twice
and encrypt the client secret using password based encryption.
Let me know what do you think and I will start to file Jiras to myself.
Note: This is not an issue specific to iOS. All the projects will get
the same love and feedback.
now that the 1.0.0-final is pretty much out for the UnifiedPush Server, i’m starting to look at the new API that Chrome apps use for sending push notifications.
the TL;DR of it is, it’s basically the same as Android now.( no more refresh tokens and access tokens and such )
So the question is, do we need to have a deprecation period on what is currently there?
The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. https://developer.chrome.com/apps/cloudMessagingV1
While i have looked to deeply, it’s possible we can use the same “Variant” structure for Chrome Apps, Since they will be using the same Network
I opened a new thread for this to make it easier to follow up on this
I just tested my Push Server and iOS just worked fine. Here are a few
* Did you upload the correct .p12 file for the iOS variant?
* Or did you replace a development cert with a production cert ?
* Did it work a few days ago?
* Did you try to reboot the instance via the openshift UI ?
On Tue, Jan 27, 2015 at 1:08 PM, Sekar, Harini <harini.sekar(a)rntbci.com>
> Hi guys,
> Have deployed the aerogear in openshit and push notification for IOS is
> not working
> Error :
> reason: Error sending payload to APNs server:
> sun.security.validator.ValidatorException: No trusted certificate found
> please help me sort this out
> Thanks & Regards
> Harini S
I've just submitted a PR to support ADM (Amazon Device Messaging) on UPS
, yay !
A few notes :
- The Java ADM connector is also managed by AeroGear , it's not yet
on Maven Central, so you will need to clone it and build it
- The Client SDK (and updated Cordova Plugin) is not yet available but
to make this PR testable, we have adapted a Cordova App that Amazon use as
sample to show ADM, this fork will register with UPS , this app contains
also all the instructions to get started
- About the client SDK, FireOS (Amazon's OS) is almost "just" Android,
so we should be able to reuse most of our Android Lib , we jsut need to
remove the GCM part and use the ADM library instead. I will start work on
that today and ping our Android gods to see which is the best way to do
So anyone who has a Amazon Tablet, please give it a shot and report on the
Have fun !