-
Notifications
You must be signed in to change notification settings - Fork 114
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
2 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -3,12 +3,12 @@ e-mission phone app | |
|
||
This is the phone component of the e-mission system. | ||
|
||
:sparkles: This has now been upgraded to cordova [email protected] and [email protected] (details). It also now supports CI, so we should not have any build issues. | ||
:sparkles: This has now been upgraded to cordova [email protected] and [email protected] ([details](https://github.com/e-mission/e-mission-docs/issues/519)). It also now supports CI, so we should not have any build issues in the future. | ||
|
||
The current limitations are: | ||
- [trip end notifications have some minor issues](https://github.com/e-mission/e-mission-transition-notify/issues/25): I will handle this as part of the upcoming upgrade to even newer cordova versions | ||
- [OpenID auth code has not been tested](https://github.com/e-mission/e-mission-docs/issues/519): It would be great if somebody who is using OpenIDAuth is able to report on testing results | ||
- [Push notifications on iOS require setting `IS_GCM_ENABLED` to `<false>` in `GoogleServices.json`](https://github.com/e-mission/e-mission-docs/issues/437#issuecomment-513506146) | ||
- [Push notifications on iOS require setting `IS_GCM_ENABLED` to `<false>` in `GoogleServices.plist`](https://github.com/e-mission/e-mission-docs/issues/437#issuecomment-513506146) | ||
|
||
:construction: There are now newer versions of cordova available. Since I am making these changes anyway, I plan to spend a day or two finishing the upgrade to [email protected] (released 29 Jun 2020) and [email protected] (released 23 Jun 2020). Hopefully, that will keep us going for a while longer without needing maintenance updates. | ||
|
||
|