D-Sek App

This app is a mobile version of our page available at https://dsek.se. The app is "simply" a WebView wrapper around https://dsek.se. There are some extra features regarding deep-linking, notifications, dark/light mode and app-specific information which are added by the app.

The goal is, and probably should always be, to keep the app AS SIMPLE AS POSSIBLE. This way ALMOST ALL updates can be done purely by releasing a new version of the site and no changes needs to be done by the app.

Communication between app and website

To communicate events and data between the app and website native window events are used. For example, the event appSendPushNotification is dispatched containing the notification token from the app.

How to deploy

Android

1. Build with npm run deploy:android or npm run deploy:android:local (from package.json)
2. Wait for the build to complete
3. Submit the app

Submitting with Expo

1. Make sure you have a google-service-account.json file, follow steps here if you dont: https://github.com/expo/fyi/blob/main/creating-google-service-account.md
2. We already have a service account, just go to google cloud platform and save it in the root directory (should not be committed).
3. Run npm run submit:android

Submitting manually

1. Download the .aab file (it will be in the project root directory if built locally)
2. Go to Google Play Console
3. Go to "Production" > "Create New Release"
4. Upload the file and add relevant changelog notes
5. Send to review and wait for it to finish

iOS

1. Build with npm run deploy:ios (from package.json)
2. Login with our apple account
3. Wait for the build to complete
4. Submit

Submitting expo

1. Run npm run submit:ios
2. Login with our apple account

Submitting manually

1. Download the .ipa file (it will be in the project root directory if built locally)
2. Use the "transporter" app (only available on MacOS) to upload the .ipa file to App Store Connect.
3. On app store connect:
   1. Go to "My Apps"
   2. Go to "D-sektionen"
   3. Create a new version next to "iOS App"
   4. Go down to "Builds" and select the newest built version (might take some minutes to appear after upload)
   5. It will say "Missing Compliance", click "Manage" and answer the questions. As of writing the answers are "Standard encryption algorithms instead of, or in addition to, using or accessing the encryption within Apple's operating system" and "Not available in France"
   6. Under "What's new in this version" add some changelog notes
   7. Click "Save" and "Add to review", then "Send to review"
   8. Wait for review to complete. (It happens that we get rejected, usually just small fixes though)

Building locally

Using the scripts (from package.json) that end in :local it is possible to build locally instead of building on Expo's servers. To set this up follow the guide on https://docs.expo.dev/get-started/set-up-your-environment/?mode=development-build&buildEnv=local&platform=android&device=physical except npx expo install expo-dev-client

The scripts npx expo run:android and npx expo run:ios (specifically expo prebuild) will generate an android/ or ios/ directory. This will cause eas build to complain about bare workflow. To fix this, simply remove the android/ or ios/ directory.

How to update

Using expo-updates we can send updates to devices without requiring them to update their app via their app store. Only javascript updates can be sent, no native code changes. See expo-updates own documentation for more detailed information.

Updates can be sent running npm run send-update, pick an update message (latest commit message by default), then waiting for the process to complete. That's it, the update will now be installed the next time each user restarts their app.

Testing updates

If you want to test a feature, you can run npm run preview (or npm run preview:ios or npm run preview:android), get a build that you can install locally on a device.

Afterwards just call npm run preview-update to test an update.