Updating app samples to make use of new SubscribeToSyncScopesWithResultAsync API which will return the UNSID for the appservice to post notifications thru MSGraph
1. Updated CDPTraces.log file location on disk, for v1.3, it has moved from external to intrenal.
2. We need to deserialize saved AAD account also during Platform initialization.
[Android][OneRomanApp] Changing client side server-key to FCM
We need to update our OneRomanApp app to use FCM, since GCM is being shutdown on April 11th. This process involves
- Change client to use FCM using the legacy key (Verified)
- Change client to use FCM generated server-key (Verified however as this in in our Secrets and google-services.json, this PR will not contain these values)
- Update the server (WNS) to use the FCM generated server-key (Will occur once we have a nightly and version of this change in HockeyApp)
If we immediately change the sever to point to the FCM server-key then existing apps using the legacy key will stop receiving notifications.
How Verified
I first deployed the changes and saw registration completed successfully.
Updating the GraphNotificationsSample to follow initialization patterns of the sdksample. It is fairly complicated setup, so it is recommended that all app developers try to follow the model laid out by this sample pretty closely. It shows how to synchronize accounts with a token library at startup, perform per account initialization as fast as possible to let incoming notifications be quickly processed and has a reusable manager object that is not tightly coupled to UI.
Removing use of 1.8 Java APIs on SDK sample.
**How Verified**
Builds with `Android\samples PS>.\gradlew --refresh-dependencies sdksample:build`. Went through signin and init correctly.
**How Verified**
Ran through the first time sign-in. Initialization went through the entire process successfully. I then went through the loading from cache flow and that also didn't appear to hit any problems.
Nearshare Standalone app updates to work with onesdk:
Verification:
1. Discovery: Launch the NearShare App and select check box "Spatially Proximal"
At this point, Platform is initialized and started and users can see list of spatially proximal devices.
2. Send URI: Select a device from the list and click "Send Uri"
You will see a toast on the target device with the uri that users can click and launch.
3. Send File(s): Go to photos app or pick any file(s) and select share, pick NearShare app
This will open the NearShareApp, continue to select checkbox "Spatially Proximal"
Select the device you want to send the file to and click "Send Files" from app
Toast will pop up on the target device with options to accept or decline
4. On clicking accept, file transfer with complete and the users can open\save the file.
Description:
The namespace/package/framework for Commanding and Hosting are now combined into a single namespace called RemoteSystems.Commanding. Adjust the samples to use the new name.
The new event model has a different access pattern for setting callbacks and unsubscribing from events. Additionally, the new Rome SDK requires Java 8 so update build.gradle files to match.
Description:
This change brings in the GraphNotificationSample to the overall build.gradle, updates it to build and ensures that the iOS counterpart builds as well.
Fixing comment in LaunchFragment.openAppServiceConnection
In the Android LaunchFragment class, Step #1, it says the method will add listeners for the AppServiceConnection’s Request Received event and Close event, but those listeners aren't in the code.
Sudipta Dey (WDG)
Nate Peterson
Hank Fox
Andrew Peacock
Brian Bowman
Andrew Peacock
Subha Santhanam
Rajat Rastogi
AJ Ballway