Add Documentation for Android Deep Link Handling #12075
Conversation
alperozturk96
changed the title
alperozturk96
force-pushed
the
add-deep-link-handling-android
branch
from
f192dba
to
2e330ae
Compare
alperozturk96
force-pushed
the
add-deep-link-handling-android
branch
from
046ea76
to
15186a8
Compare
admin_manual/configuration_server/android_deep_link_handling.rst
Outdated
Show resolved
Hide resolved
admin_manual/configuration_server/android_deep_link_handling.rst
Outdated
Show resolved
Hide resolved
admin_manual/configuration_server/android_deep_link_handling.rst
Outdated
Show resolved
Hide resolved
admin_manual/configuration_server/android_deep_link_handling.rst
Outdated
Show resolved
Hide resolved
admin_manual/configuration_server/android_deep_link_handling.rst
Outdated
Show resolved
Hide resolved
admin_manual/configuration_server/android_deep_link_handling.rst
Outdated
Show resolved
Hide resolved
| Replace APP_SHA256_FINGERPRINT with the SHA-256 fingerprint of your app’s | ||
| signing certificate. |
There was a problem hiding this comment.
Oh, this is only applicable to branded apps, right?
This either needs a big caveat at the top of the chapter or maybe it shouldn't be included here since it's not applicable to community users... so maybe it only belongs in the customer docs in https://portal.nextcloud.com somewhere?
There was a problem hiding this comment.
@alperozturk96 this also works for our official app, right?
So maybe add the sha256 of our app here.
And as Josh suggested, add a portal entry how this needs to be changed for branded apps.
There was a problem hiding this comment.
@tobiasKaminsky How can I add portal entry?
There was a problem hiding this comment.
The globbing recently added in #11691 should pick it up. :-) |
Signed-off-by: alperozturk <[email protected]>
Signed-off-by: alperozturk <[email protected]>
Co-authored-by: Josh <[email protected]> Signed-off-by: Alper Öztürk <[email protected]> Signed-off-by: alperozturk <[email protected]>
Co-authored-by: Josh <[email protected]> Signed-off-by: Alper Öztürk <[email protected]> Signed-off-by: alperozturk <[email protected]>
Co-authored-by: Josh <[email protected]> Signed-off-by: Alper Öztürk <[email protected]> Signed-off-by: alperozturk <[email protected]>
Co-authored-by: Josh <[email protected]> Signed-off-by: Alper Öztürk <[email protected]> Signed-off-by: alperozturk <[email protected]>
Co-authored-by: Josh <[email protected]> Signed-off-by: Alper Öztürk <[email protected]> Signed-off-by: alperozturk <[email protected]>
Signed-off-by: alperozturk <[email protected]>
Signed-off-by: alperozturk <[email protected]>
alperozturk96
force-pushed
the
add-deep-link-handling-android
branch
from
f4a1b27
to
21ebe10
Compare
Co-authored-by: Josh <[email protected]> Signed-off-by: Alper Öztürk <[email protected]>
|
Is this intended as an alternative approach to nextcloud/server#44665? |
No, that PR is only functional for us. If a user wants to use it with a different server name, it will not work on Android 12 or above. For more details |
☑️ Resolves
This pull request includes documentation for handling deep links in Android applications, specifically addressing the requirements and configurations for Android 12 and above.
🖼️ Screenshots