We want to move our AeroGear Push server to Amazon. We are looking into using either EC2 or their Container Service. Is there any pros/cons w eshould know about?
Is one or the other a perferred choice?
Secondly, are there any migration process, or do we just copy/paste the database to the new server? I cannot find any information regarding this.
T: +45 42 42 80 60
M: +45 20 28 20 26
I am wondering what your progress on implementing the new iOS 10 rich nofitications is and/or whether you have a time schedule about when it will be available. Thank you for your reply.
-- Disclaimer --
Vlaamse Radio- en Televisieomroeporganisatie
Auguste Reyerslaan 52
nv van publiek recht
BTW BE 0244.142.664
VRT Gebruikersvoorwaarden <http://www.vrt.be/gebruiksvoorwaarden>
There's a big change to the AeroGear iOS OAuth2 library: it's now been
migrated to Swift 3! 🎉🎉🎉 It still needs to be published to the main
CocoaPods Specs repo for wider adoption (all 65 GitHub stars' worth), so if
you want to use it, for now point your Podfile to the AeroGear repo. There
are also three pending pull requests that I'd appreciate a review on:
* #64 Update Podspec - A simple PR to update the version of the AeroGear
iOS Http library that is required by the library
* #63 Add audience and server code - This allows developers to validate the
refresh/access token request being made as well as do cross-client auth so
a mobile app and server backend are essentially viewed as one application
to be authorized
* #62 Add ID token to auth response - Many OAuth2 providers now send a JWT
ID token along with the other usual tokens that provides extra information
about a user, e.g., user ID, address, phone number, etc.
These PRs are pretty small, but I think add some good functionality to the
library! My next planned pieces of work are:
* Switch Google to use SFSafariViewController - Per a post on the Google
dev blog (
they will soon be disallowing embedded web views to do the OAuth2 dance.
The solution is to use SFSafariViewController (or just the regular Safari
browser). This already exists in the library, but Google needs to be
special-cased to never accept an embedded web view as an option.
* Better cookie management to support multiple accounts - Some services
(like Google) provide an account picker for a user to choose from. This is
a much better UX. However, not all OAuth2 providers are as cool as Google.
For these providers, you cannot currently sign into multiple accounts using
the OAuth2 library unless you clear cookies before the embedded web view is
presented. Will be working on a solution to do this.
Hello iOS lovers,
Swift3 is coming!
Today we released to CocoaPods aerogear-ios-http 1.0.0 for Swift3.
Thanks tuzonghua for reviewing and help.
aerogear-ios-push Swift3 is coming next.
aerogear-ios-oauth2 is progressing. @tuzonghua, PR welcome ;)
Community contribution on Swift3 migration is welcome!
PS: I love new emoji from CocoaPods:
[image: Inline images 1]
summers pointed out that the "Server Key(s)" in FCM are being deprecated,
and replaced by a "Firebase Cloud Messaging token".
In the Firebase API Console, I read the following for the Cloud Messaging
"Firebase Cloud Messaging tokens have replaced server keys for sending
messages. While you may continue to use them, support is being deprecated
for server keys."
OK, that's an easy change for us: It works the same. We need to change the
UI to reflect the new name - that's all.
I just tested a successful FCM push (WebPush to Chrome), using UPS 1.1.x,
with the generated token instead of the server-key. All continues to be
BTW. In the Firebase Console, I did not see this yesterday morning (German
time), they must have added it later the day :-)
Hey peeps, There was an issue on stack overflow,
The notification would be sent ok, but the node clients promise would
always be rejected, it turns out we were looking for a 200 status, and not
a 202(which is what is returned and defined in the REST api docs).
I've updated this and pushed out a 0.14.1 release on Saturday night.
possible that there may be problems w/ the migration from a 1.0.x version
On Thu, Nov 3, 2016 at 1:45 PM, Sonu Kumar Gupta <
> Dear Sir,
> Pls. help
> I am starting wildfly with ./standalone.sh --server-config=standalone-full.xml
> It works without errors.
> I cloned latest aerogear-unifiedpush-server and installed with maven
> I follow the steps in https://aerogear.org/docs/unifiedpush/ups_userguide/
> I am using postgres database. It is running on localhost and the port is
> 5432. postgres connector version is postgresql-9.4.1207.jar.
> I created all databases. Generated the UnifiedPush Database and Datasource.
> liquibase.properties contains the following info
> *ON STEP 'CREATE THE DATABASE SCHEMA'*
> I run ./bin/ups-migrator update
> I get the error 'Unexpected error running Liquibase: Precondition error'
> Sonu Kumar Gupta
> Aerogear-users mailing list