Appsflyer Request: Delayed start
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 45/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- react-native, typescript
- Domain
- mobile-dev
Research direction
Start by locating the AppsflyerPlugin implementation and tracing how initSdk and startSdk are invoked when the plugin is added. Check the plugin lifecycle and existing tests, if present, then define and verify behavior where initialization remains available but starting waits until consent is supplied.
Written by the indexing model from the issue text.
Description
Hi we are ensuring our app & data pipeline adheres to GDPR. That means that we have implemented a CMP to collect consent, then we add the consent object to each segment event, no problem!
We've ran into an issue with Appsflyer, because it doesn't send it's data via Segment in the cloud, it sends data directly from the device with it's own SDK, and then tells Segment it happened, which fires an event.
We'd like appsFlyer.startSdk(); to be called after we have shown the CMP and obtained the users consent, so we can set the consent (with appsFlyer.setConsentData()). The init: appsFlyer.initSdk can still be called when we add the plugin.
We are doing this:
const segmentClient = createClient({...etc})
segmentClient.add({ plugin: new AppsflyerPlugin() });
Now, as it stands, the AppsflyerPlugin inits and starts Appsflyer. What is the best way for me to keep the init, but delay the start of Appsflyer? I can't add a consent param to the constructor, because I don't know the consent yet.
Do I just edit the code for the plugin to add this consent param, and if it's not given, only init, then remove + re-add the plugin later when consent is given? This is the main thing I can think of atm.
Hope this makes sense. Thanks.
- Dominant language
- TypeScript
- Stars
- 384
- Forks
- 205
- Avg merge
- 12h 17m
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from segmentio/analytics-react-native
-
chunk() never resets its size counter: past 500 KB every queued event is uploaded as its own requestOpen
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
segmentio/analytics-react-native#1334 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug investigate
Difficulty 1/5 Under an hour Newbie friendliness 72/100
segmentio/analytics-react-native#1145 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 68/100
segmentio/analytics-react-native#1328 ·
Maintainers usually reply within 1 day
-
bug investigate
Difficulty 3/5 1-2 days Newbie friendliness 78/100
segmentio/analytics-react-native#1309 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 3/5 1-2 days Newbie friendliness 48/100
segmentio/analytics-react-native#1114 ·
Maintainers usually reply within 1 day
All issues in segmentio/analytics-react-native
Similar issues
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
inu-appcenter/memorIN-frontend#106 ·
Maintainers usually reply within 1 day
-
kind/bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 7 days
-
[Bug] @deck.gl/arcgis dist import resolves to unpublished @deck.gl/core source path (9.3.11, 9.4.0)Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
CSCfi/sd-search-ui#145 ·
Maintainers usually reply within 1 day
-
Add: Cbeebies pl SDOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day