Skip to content

Commit daa8fa9

Browse files
authored
Add info about affected app services (#3383)
## Pull Request Info - SDK Docs Consolidation Add more information to the deprecations page about App Services that are affected by SDK deprecation since they rely on the SDKs. ### Staging Links <!-- start insert-links --> <li><a href=https://deploy-preview-3383--device-sdk.netlify.app/deprecation>deprecation</a></li> <!-- end insert-links -->
1 parent e7666fd commit daa8fa9

File tree

1 file changed

+52
-6
lines changed

1 file changed

+52
-6
lines changed

source/deprecation.txt

+52-6
Original file line numberDiff line numberDiff line change
@@ -25,14 +25,60 @@ move to an alternative solution or remove Sync before September 30, 2025. Refer
2525
to the :ref:`App Services deprecation page <app-services-deprecation>` for more
2626
information.
2727

28+
Additional Impacted App Services Capabilities
29+
---------------------------------------------
30+
31+
Some App Services are affected by the deprecation of the Device SDKs. These
32+
services will no longer function as expected when the SDKs reach end-of-life and
33+
are not supported.
34+
35+
Authentication and User Management
36+
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
37+
38+
The Device SDKs are the primary entry point for :ref:`App Services
39+
Authentication and User Management <users-and-authentication>`, an
40+
authentication service for your applications. As part of the SDK deprecation,
41+
this feature will no longer be available when the SDKs reach end-of-life and are
42+
removed. You must move to an alternative authentication service before that time
43+
to avoid disruption in your application.
44+
45+
The feature supports multiple :ref:`authentication providers
46+
<authentication-providers>`, and your migration to alternative solutions depends
47+
on your provider. To identify the best alternative for your use case, please
48+
contact your Account team.
49+
50+
Given App Services Authentication is no longer available, Authentication
51+
Triggers will no longer be executed when user events (for example: login or
52+
create) occur. This authentication logic will need to be implemented along with
53+
the chosen alternative solution.
54+
55+
Functions
56+
~~~~~~~~~
57+
58+
Functions will continue to be available within the context of Triggers. Use
59+
cases where a function was being directly accessed through a Realm SDK are
60+
impacted and must migrate to a different solution.
61+
62+
Wire Protocol
63+
~~~~~~~~~~~~~
64+
65+
App Services Wire Protocol is also deprecated alongside the Realm SDKs.
66+
67+
Data Access Permissions
68+
~~~~~~~~~~~~~~~~~~~~~~~
69+
70+
Data Access Permissions (Rules and Roles) are also deprecated alongside Device
71+
Sync.
72+
2873
Device SDKs Community Branches
2974
------------------------------
3075

3176
The Device SDKs will have community branches that remove Device Sync code from
32-
their codebases. Learn more in the SDKs' README files:
77+
their codebases. Check out the community branches for the following SDKs:
3378

34-
- `Flutter <https://github.com/realm/realm-dart>`__
35-
- `Kotlin <https://github.com/realm/realm-kotlin>`__
36-
- `.NET <https://github.com/realm/realm-dotnet>`__
37-
- `JavaScript <https://github.com/realm/realm-js>`__
38-
- `Swift <https://github.com/realm/realm-swift>`__
79+
- `C++ <https://github.com/realm/realm-cpp/tree/community>`__
80+
- `Flutter <https://github.com/realm/realm-dart/tree/community>`__
81+
- `Kotlin <https://github.com/realm/realm-kotlin/tree/community>`__
82+
- `.NET <https://github.com/realm/realm-dotnet/tree/community>`__
83+
- `JavaScript <https://github.com/realm/realm-js/tree/community>`__
84+
- `Swift <https://github.com/realm/realm-swift/tree/community>`__

0 commit comments

Comments
 (0)