@binoban/react-native 1.0.0 → 1.0.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -20
- package/README.md +19 -113
- package/package.json +4 -4
package/LICENSE
CHANGED
|
@@ -1,20 +1,201 @@
|
|
|
1
|
-
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright 2025 Binoban
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,6 +1,10 @@
|
|
|
1
1
|
# @binoban/react-native
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
> **Binoban is an enterprise CDXP infrastructure platform for customer data, activation, retail media, advertising, governance, and decisioning.**
|
|
4
|
+
|
|
5
|
+
The official **React Native SDK** for Binoban — a thin New-Architecture TurboModule bridge over the native Binoban SDKs (Android `io.binoban.sdk:sdk-android` on Maven Central; iOS `binoban` XCFramework on CocoaPods). Use it to send customer events, identity, and consent-aware signals from a React Native app into a Binoban deployment, and to receive Binoban push-notification interactions.
|
|
6
|
+
|
|
7
|
+
Built for enterprise, on-premise, private, and white-label deployment models. Full documentation: **[docs.binoban.io](https://docs.binoban.io)**.
|
|
4
8
|
|
|
5
9
|
## Installation
|
|
6
10
|
|
|
@@ -26,7 +30,7 @@ on any device or OS version. Failures are swallowed and logged only when
|
|
|
26
30
|
|
|
27
31
|
```ts
|
|
28
32
|
const client = createClient({
|
|
29
|
-
apiHost: '
|
|
33
|
+
apiHost: 'api.binoban.io',
|
|
30
34
|
credentials: { android: { /* ... */ }, iOS: { /* ... */ } },
|
|
31
35
|
onError: (e) => console.warn('Binoban:', e.method, e.message),
|
|
32
36
|
});
|
|
@@ -108,121 +112,23 @@ it in your handler.
|
|
|
108
112
|
|
|
109
113
|
---
|
|
110
114
|
|
|
111
|
-
##
|
|
112
|
-
|
|
113
|
-
### Prerequisites
|
|
114
|
-
|
|
115
|
-
- Node >= 20 (`nvm use` to switch automatically)
|
|
116
|
-
- Yarn 4 (`corepack enable` if needed)
|
|
117
|
-
- **iOS only:** Ruby via `rbenv` or `rvm`, CocoaPods managed through Bundler
|
|
118
|
-
|
|
119
|
-
### First-time setup
|
|
120
|
-
|
|
121
|
-
```sh
|
|
122
|
-
# 1. Install JS dependencies
|
|
123
|
-
yarn
|
|
124
|
-
|
|
125
|
-
# 2. iOS only — install the Bundler-locked version of CocoaPods and run pod install
|
|
126
|
-
cd example/ios
|
|
127
|
-
bundle install
|
|
128
|
-
bundle exec pod install
|
|
129
|
-
cd ../..
|
|
130
|
-
```
|
|
131
|
-
|
|
132
|
-
> Always use `bundle exec pod install` (not bare `pod install`) to use the exact CocoaPods version from the Gemfile.lock.
|
|
133
|
-
|
|
134
|
-
---
|
|
135
|
-
|
|
136
|
-
## Running the example app
|
|
137
|
-
|
|
138
|
-
### Android
|
|
139
|
-
|
|
140
|
-
```sh
|
|
141
|
-
yarn example android
|
|
142
|
-
```
|
|
143
|
-
|
|
144
|
-
### iOS
|
|
145
|
-
|
|
146
|
-
```sh
|
|
147
|
-
yarn example ios
|
|
148
|
-
```
|
|
149
|
-
|
|
150
|
-
`automaticPodsInstallation` is enabled in `example/react-native.config.js`, so `yarn example ios` will trigger `pod install` automatically when Pods are out of date. If it doesn't pick up your changes, run manually:
|
|
151
|
-
|
|
152
|
-
```sh
|
|
153
|
-
cd example/ios && bundle exec pod install && cd ../..
|
|
154
|
-
```
|
|
155
|
-
|
|
156
|
-
To start Metro separately (useful for attach/reload without rebuilding):
|
|
157
|
-
|
|
158
|
-
```sh
|
|
159
|
-
yarn example start
|
|
160
|
-
```
|
|
161
|
-
|
|
162
|
-
---
|
|
163
|
-
|
|
164
|
-
## What to do after common changes
|
|
165
|
-
|
|
166
|
-
### Changing `src/NativeBinobanReactNative.ts` (the TurboModule spec)
|
|
167
|
-
|
|
168
|
-
The spec drives ObjC++ codegen on iOS and Kotlin codegen on Android.
|
|
169
|
-
|
|
170
|
-
**iOS** — regenerate codegen by running pod install:
|
|
171
|
-
```sh
|
|
172
|
-
cd example/ios && bundle exec pod install && cd ../..
|
|
173
|
-
```
|
|
174
|
-
The generated files land in `example/ios/build/generated/ios/ReactCodegen/BinobanReactNativeSpec/`. Then rebuild the app normally with `yarn example ios`.
|
|
175
|
-
|
|
176
|
-
**Android** — no manual step. The Android Gradle plugin regenerates the spec automatically during the next build (`yarn example android`).
|
|
115
|
+
## Documentation
|
|
177
116
|
|
|
178
|
-
|
|
117
|
+
- **Developer documentation:** https://docs.binoban.io
|
|
118
|
+
- **Website:** https://binoban.io
|
|
179
119
|
|
|
180
|
-
|
|
181
|
-
|
|
182
|
-
|
|
183
|
-
```
|
|
184
|
-
|
|
185
|
-
Metro hot-reload does **not** pick up native changes.
|
|
186
|
-
|
|
187
|
-
### Changing JS/TS source only (`src/*.ts`, `src/*.tsx`)
|
|
188
|
-
|
|
189
|
-
Metro picks these up automatically — no rebuild needed. If the example app is already running, save the file and Metro will hot-reload.
|
|
190
|
-
|
|
191
|
-
---
|
|
120
|
+
Credentials (`apiKey`, `sourceIdentifier`) and your deployment `apiHost` are issued by
|
|
121
|
+
Binoban — contact **support@binoban.io**. `api.binoban.io` is the Binoban-hosted host;
|
|
122
|
+
on-premise / white-label deployments use their own.
|
|
192
123
|
|
|
193
|
-
##
|
|
124
|
+
## Security
|
|
194
125
|
|
|
195
|
-
|
|
126
|
+
Report vulnerabilities privately to **security@binoban.io** — please do not open a public
|
|
127
|
+
issue. The snippets here use placeholder credentials only; never commit real API keys,
|
|
128
|
+
source identifiers, or non-production hosts.
|
|
196
129
|
|
|
197
|
-
|
|
198
|
-
|
|
199
|
-
The fix is already wired into `example/ios/Podfile`: its `post_install` hook patches `Pods/fmt/include/fmt/base.h` to disable `fmt`'s `consteval` path (compile-time format-string checking off; runtime formatting unchanged). It re-applies automatically on every `pod install`. If you still hit the error, re-run `pod install` and confirm you see `Patched fmt base.h …` in the output, then clean the build folder (Xcode → Product → Clean Build Folder) and rebuild.
|
|
200
|
-
|
|
201
|
-
---
|
|
202
|
-
|
|
203
|
-
## Opening native code in an IDE
|
|
204
|
-
|
|
205
|
-
**Xcode (iOS):**
|
|
206
|
-
Open `example/ios/BinobanReactNativeExample.xcworkspace` (the `.xcworkspace`, not `.xcodeproj`). The bridge source files are under `Pods > Development Pods > binoban-react-native`.
|
|
207
|
-
|
|
208
|
-
**Android Studio:**
|
|
209
|
-
Open `example/android`. The bridge source files appear under `binoban-react-native` in the project tree.
|
|
210
|
-
|
|
211
|
-
---
|
|
212
|
-
|
|
213
|
-
## Other commands
|
|
214
|
-
|
|
215
|
-
```sh
|
|
216
|
-
yarn typecheck # TypeScript type check
|
|
217
|
-
yarn lint # ESLint
|
|
218
|
-
yarn lint --fix # Auto-fix lint issues
|
|
219
|
-
yarn test # Jest unit tests
|
|
220
|
-
yarn prepare # Build the library (outputs to lib/)
|
|
221
|
-
yarn release # Publish to npm (bumps version, tags, creates GitHub release)
|
|
222
|
-
```
|
|
223
|
-
|
|
224
|
-
---
|
|
130
|
+
## License & status
|
|
225
131
|
|
|
226
|
-
|
|
132
|
+
Apache-2.0 — see [LICENSE](LICENSE). Matches the Binoban native SDKs this bridge wraps.
|
|
227
133
|
|
|
228
|
-
|
|
134
|
+
Stable — released as `@binoban/react-native` **1.0.0**.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@binoban/react-native",
|
|
3
|
-
"version": "1.0.
|
|
3
|
+
"version": "1.0.1",
|
|
4
4
|
"description": "React Native SDK for Binoban",
|
|
5
5
|
"main": "./lib/module/index.js",
|
|
6
6
|
"types": "./lib/typescript/src/index.d.ts",
|
|
@@ -51,12 +51,12 @@
|
|
|
51
51
|
"type": "git",
|
|
52
52
|
"url": "git+https://github.com/binoban/binoban-example-react-native.git"
|
|
53
53
|
},
|
|
54
|
-
"author": "
|
|
55
|
-
"license": "
|
|
54
|
+
"author": "Binoban Engineering <tech@binoban.io> (https://docs.binoban.io)",
|
|
55
|
+
"license": "Apache-2.0",
|
|
56
56
|
"bugs": {
|
|
57
57
|
"url": "https://github.com/binoban/binoban-example-react-native/issues"
|
|
58
58
|
},
|
|
59
|
-
"homepage": "https://
|
|
59
|
+
"homepage": "https://docs.binoban.io",
|
|
60
60
|
"publishConfig": {
|
|
61
61
|
"registry": "https://registry.npmjs.org/",
|
|
62
62
|
"access": "public"
|