React Native - OneSignal Proxy

30 Jul 2019

Nginx
OneSignal-Android-SDK
OneSignal-iOS-SDK
react-native-onesignal
your application

https://github.com/geektimecoil/react-native-onesignal/issues/615#issuecomment-416441323

You would need to remove OneSignal from your build.gradle and you would need to manually download the Android and iOS native SDK’s (links below) and modify them to change the URL.

Once you change the URL, you’ll need to recompile both of them, compile Android SDK into a jar, and you can compile the iOS SDK into a framework or a static library, or even host it as a private cocoapod.

Nginx

configure Nginx as a reverse proxy to proxy requests to https://onesignal.com:

  # /etc/nginx/sites-available/<MY_APP>_production

  server {
    listen 443 ssl;

    # ...

+   location /onesignal/ {
+     proxy_pass https://onesignal.com/;
+   }
  }

OneSignal-Android-SDK

fork and clone https://github.com/OneSignal/OneSignal-Android-SDK

$ git clone git@github.com:<MY_COMPANY>/OneSignal-Android-SDK.git
$ cd OneSignal-Android-SDK
$ git checkout 3.11.1
$ git checkout -b <MY_APP>

3.11.1 is the version used by your application (as a dependency of react-native-onesignal npm package):

// node_modules/react-native-onesignal/android/build.gradle

dependencies {
    // ...

    implementation('com.onesignal:OneSignal:3.11.1') {
        exclude group: 'com.android.support'
    }
}

though not strictly necessary, it’s better to stick to the same version of OneSignal-Android-SDK plugin in your fork since it must have been already tested against react-native-onesignal npm package.

change BASE_URL in OneSignalRestClient.java

  // onesignal/src/main/java/com/onesignal/OneSignalRestClient.java

- private static final String BASE_URL = "https://onesignal.com/api/v1/";
+ private static final String BASE_URL = "https://<PROXY_HOST>/onesignal/api/v1/";

build Android library
https://developer.android.com/studio/projects/android-library
```
apply plugin: 'com.android.library'
```
The entire structure of the module remains the same, but it now operates as an Android library and the build will now create an AAR file instead of an APK.
```
$ cd OneSignalSDK
$ chmod +x gradlew
$ ./gradlew build -x test
```
output file: OneSignalSDK/onesignal/build/outputs/aar/onesignal-release.aar (we don’t need other files).

OneSignal-iOS-SDK

fork and clone https://github.com/OneSignal/OneSignal-iOS-SDK

$ git clone git@github.com:<MY_COMPANY>/OneSignal-iOS-SDK.git
$ cd OneSignal-iOS-SDK

change SERVER_URL in OneSignalCommonDefines.h

  // iOS_SDK/OneSignalSDK/Source/OneSignalCommonDefines.h

- #define SERVER_URL @"https://onesignal.com/"
+ #define SERVER_URL @"https://<PROXY_HOST>/onesignal/"

build static library

https://stackoverflow.com/a/22556684/3632318

open iOS_SDK/OneSignalSDK/OneSignal.xcodeproj in Xcode

select scheme and destination

Xcode
`Product` (top menu) → `Scheme` → `OneSignal-Static-Framework`
`Product` (top menu) → `Destination` → `Generic iOS Device`

it’s necessary to build library not only for armv7 and arm64 but for i386 and x86_64 architectures as well because actual device uses ARM processor while simulator uses Intel processor (your host machine):

https://www.quora.com/Why-do-I-need-x86_64-architecture-under-xcode-while-compiling-an-iOS-app/answers/24349415

You will build for the following architectures:

armv7 - for 32-bit devices

arm64 - for 64-bit devices

i386 - for simulators of 32-bit devices

x86_64 - for simulators of 64-bit devices

The simulators run code natively on the computer so they are x86. You will only submit armv7 and arm64 to the store.

in the end your application will fail to build in Xcode if it’s linked with a static library supporting armv7 and arm64 architectures only.

the problem is that if you select OneSignal scheme (and OneSignal target accordingly), you’ll be able to build for armv7 and arm64 architectures only - manually adding i386 and x86_64 architectures in Build Settings of OneSignal target will cause the build of static library to fail.

but OneSignal-Static-Framework scheme runs build_fat_framework.sh script which seems to solve this problem by creating a universal binary file:

# iOS_SDK/OneSignalSDK/build_fat_framework.sh

# Generates a universal/fat framework that can be used in multiple
# architectures (x86_64 and arm64) to support both simulator and actual
# devices.

# Build x86 based framework to support iOS simulator
# ...

# Build arm based framework to support actual iOS devices
# ...

# Combine results
# use lipo to combine device & simulator binaries into one
# ...

output file: iOS_SDK/OneSignalSDK/Framework/OneSignal.framework/OneSignal - (it’s a symlink which points to a static library).

use lipo to check a static library contains all required architectures:

$ lipo -archs OneSignal
armv7 i386 x86_64 arm64