-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SDK-3289] Update miscellaneous references and code snippets for Swift SDK #5235
[SDK-3289] Update miscellaneous references and code snippets for Swift SDK #5235
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
b334633
to
0a43b07
Compare
0a43b07
to
56cf033
Compare
@@ -293,30 +292,44 @@ Braze.getInstance(this).subscribeToSdkAuthenticationFailures({ error: BrazeSdkAu | |||
``` | |||
{% endtab %} | |||
{% tab Objective-C %} | |||
|
|||
{% alert important %} | |||
Starting in version `5.14.0` of the Braze Swift SDK, the SDK authentication delegate method has been split from the `BrazeDelegate` into a separate `BrazeSDKAuthDelegate`. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change is pending release, so we'll need to coincide this merge with the release of the new version.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jerielng Do you know the time frame of the release?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It'll be within the next week. We have most of the changes ready, just doing some final merges and reviews.
@@ -77,7 +77,7 @@ To learn more about JSON Web Tokens, or to browse the many open source libraries | |||
|
|||
This feature is available as of the following [SDK versions]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features/#filtering-by-most-recent-app-versions): | |||
|
|||
{% sdk_min_versions web:3.3.0 ios:4.3.0 android:14.0.0 %} | |||
{% sdk_min_versions web:3.3.0 ios:5.0.1 android:14.0.0 %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This linking seems to be broken for some reason. I'm not sure what's going on here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe @josh-mccrowell-braze can take a look
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One complication is that this feature is supported on:
- AppboyKit 4.3.0+
- Swift SDK 5.0.1+
Since this is removing our public docs for AppboyKit, I'm debating if we are OK with:
- Completely removing AppboyKit docs
- Removing AppboyKit docs but linking out to the sample AppboyKit code integration
- Keeping a copy of both AppboyKit docs and Swift SDK docs
I'm leaning towards 2) where at the bottom of the ObjC and Swift sections we link out to the sample code in Stopwatch, even though it's in ObjC. This would be relevant for Enable this feature in the Braze SDK
and Register a callback function for invalid tokens
sections:
For the legacy AppboyKit SDK, reference [this file]({file_here}) for sample code.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good overall - just one main point about having some links to the old AppboyKit SDK Auth integration
_docs/_developer_guide/platform_integration_guides/sdk_primer.md
Outdated
Show resolved
Hide resolved
@@ -77,7 +77,7 @@ To learn more about JSON Web Tokens, or to browse the many open source libraries | |||
|
|||
This feature is available as of the following [SDK versions]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features/#filtering-by-most-recent-app-versions): | |||
|
|||
{% sdk_min_versions web:3.3.0 ios:4.3.0 android:14.0.0 %} | |||
{% sdk_min_versions web:3.3.0 ios:5.0.1 android:14.0.0 %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe @josh-mccrowell-braze can take a look
@@ -77,7 +77,7 @@ To learn more about JSON Web Tokens, or to browse the many open source libraries | |||
|
|||
This feature is available as of the following [SDK versions]({{ site.baseurl }}/user_guide/engagement_tools/campaigns/ideas_and_strategies/new_features/#filtering-by-most-recent-app-versions): | |||
|
|||
{% sdk_min_versions web:3.3.0 ios:4.3.0 android:14.0.0 %} | |||
{% sdk_min_versions web:3.3.0 ios:5.0.1 android:14.0.0 %} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One complication is that this feature is supported on:
- AppboyKit 4.3.0+
- Swift SDK 5.0.1+
Since this is removing our public docs for AppboyKit, I'm debating if we are OK with:
- Completely removing AppboyKit docs
- Removing AppboyKit docs but linking out to the sample AppboyKit code integration
- Keeping a copy of both AppboyKit docs and Swift SDK docs
I'm leaning towards 2) where at the bottom of the ObjC and Swift sections we link out to the sample code in Stopwatch, even though it's in ObjC. This would be relevant for Enable this feature in the Braze SDK
and Register a callback function for invalid tokens
sections:
For the legacy AppboyKit SDK, reference [this file]({file_here}) for sample code.
@@ -58,23 +58,24 @@ These properties are collected by the Android SDK upon proper integration. | |||
{: .reset-td-br-1 .reset-td-br-2} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This file is named _docs/_developer_guide/platform_integration_guides/sdk_primer.md
but the title on top is SDK 101
and the content doesn't mention push primers - do we want to rename this file (+ possible redirects) @josh-mccrowell-braze?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm. The only thing that the name of the file affects (that I know of, anyway) is the URL, which is sort of low-value compared to the article title and nav title. Does the need to update the URL outweigh the risks? There's a few instances of this here and there and I generally think the update is low value.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any concern with updating the name of the file (does it break anything)? I think if it's easy and doesn't interfere with anything, it might be fine to just update the file name so it doesn't stay confusing in the future
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, I realize now that we've talked about this that the reason this is displaying this way (although the file name is still the same) is because the feature branch is outdated. That article has gotten some TLC in the meantime.
I think it's fair to change the name of the file, and will take a note to do so, but will implement on another branch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM after the changes related to AppboyKit
33d7394
to
d4d0a00
Compare
@braze-inc/sdks-web Sanity checking here, is this code snippet correct? Noticed inside the closure, it's referencing
|
@braze-inc/sdks-android Sanity check for the Java and Kotlin tabs for this section here. Seems to be referencing |
endpoint: "{YOUR-BRAZE-ENDPOINT}") | ||
configuration.api.sdkAuthentication = true | ||
let braze = Braze(configuration: configuration) | ||
AppDelegate.braze = braze | ||
``` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bump for this comment about including a way to access the example code for AppboyKit if they are using the legacy SDK
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I included it here at the top-level instead of at each code snippet - let me know what you think!
Just FYI, re: the sdk_min_version not linking correctly, that has been fixed here: #5262 |
Co-authored-by: Daniel Hok <4797040+hokstuff@users.noreply.github.com>
Pull Request/Issue Resolution
Description of Change:
These changes include updates for the Swift SDK that are outside the
Swift SDK
platform integration guide, particularly withCloses #ISSUE_NUMBER_HERE
Is this change associated with a Braze feature/product release?
✔️ Pull Request Checklist
assets
>js
>broken_redirect_list.js
⭐ Helpful Wiki Shortcuts
❗ ATTN: For PR Reviewers
❗ ATTN: Internal Reviewing Chart
Work at Braze and not sure who to tag for review?
Before tagging @josh-mccrowell-braze or @KellieHawks for a general review, reference the following chart to see if a specific product vertical/reviewer applies to your pull request.
Quality Infrastructure
Platform Infrastructure
Datalake
SDKs
Internal Tools
Product Partnerships
SMS
Customer Lifecycle, Identity and Permissions
Intelligence
User Targeting
IAM
Channels
FIX
Core Objects
Core Messaging
Messaging and Automation
Email (Composition and Infrastructure)