Sharezone is a collaborative school organization app for iOS, Android, macOS and web.

Added PushNotificationActionHandler to parse and execute actions of a PushNotification by a user provided configuration.

E.g.: If a Max added homework 'page 23 3b)' to 'math 8b' course notification comes in then this class will be invoked if the user taps on the notification. In this example invoking the PushNotificationActionHandler might result in opening the details page of the mentioned homework.

PushNotificationActionHandler doesn't implement the exact actions and parsing logic itself but rather gives an instrumented, structured and opinionated way for a client of this class to provide their own parsing and handling of PushNotification via several ActionRegistration.

A PushNotification needs to have an PushNotification.actionType (e.g. 'show-homework') which may have additional data PushNotification.actionData (e.g. {'id': 'homework-123').

Example of a PushNotification:

PushNotification({
 title: 'Max added a homework',
 body: '"S. 32 5b)" has been added to "Mathe 3a"',
 actionType: 'show-homework',
 actionData: {
  'id': 'homework-1243',
 }
});

With the PushNotification.actionType a user-provided ActionRegistration can be selected where ActionRegistration.registerForActionTypeStrings equals the PushNotification.actionType.

Then selected ActionRegistration will then be used to parse an ActionRequest from the PushNotification (e.g. ShowHomework(id: 'homework-123')) via ActionRegistration.parseActionRequestFromNotification.

The parsed ActionRequest will then be passed on ActionRegistration.executeActionRequest to execute the action of the parsed ActionRequest (e.g. open a page showing the homework with the id 'homework-123').

Example of a ActionRegistration:

final showHomeworkRegistration = ActionRegistration<ShowHomeworkRequest>(
  registerForActionTypeStrings: {'show-homework-with-id'},
  parseActionRequestFromNotification: (notification, instrumentation) =>
      ShowHomeworkRequest(HomeworkId(notification.actionData['id'])),
  executeActionRequest: (actionRequest) {
    _navigationService.pushWidget(
        HomeworkDetails.loadId('${actionRequest.homeworkId}'),
        name: HomeworkDetails.tag);
  },
);

To use it:

Create a normal notification:

Add actionType and other data (will be in actionData) as attributes:

The action types and attributes on can use can be found under app/lib/notifications/action_requests.

We are building for every PR a web preview, which will be deployed to Firebase Hosting. The link to the website will posted as comment (like: https://github.com/SharezoneApp/sharezone-app/pull/119#issuecomment-1030012299).

The previews are helping reviewer and other users to quickly view the changes in a compiled version.

A link to a preview expires after 30 days.

Closes #8

Building macOS on main resulted in the following error

[!] No podspec found for `path_provider` in `Flutter/ephemeral/.symlinks/plugins/path_provider/macos`

This seems to come from an old macOS Podfile. When Flutter creates a new Podfile many lines of code are not existing that we had in the Podfile in main.

With this PR I:

• Created a new Podfile by deleting the old one and letting Flutter create a new version (by running flutter pub get).
• Add the build time fix for Firestore.
• Update Firestore dependency (old version threw an error when running pod install)

With these fixes I can now build the macOS version again on my MacBook.

Description

We are already using the Deploy to Firebase action to deploy our web to a temporary url, when opening a new pull request.

codemagic_app_preview does the same for iOS and Android. Just scan the QR with your phone, install the app and review the changes 👍

Currently, I'm not able to build a iOS and macOS with one Codemagic workflow. Therefore, we are not building the macOS app at the moment. When I fixed this, I will make a new PR for adding support for macOS 👍

Google Sign In & Dynamic Links are not working at the moment for the Android version, because the dev Firebase project does not contain the SHA1 & SHA256 values of the code signing key (see #289).

Description

In the past, we had several times problems with building for specific platforms (see #161, #64). To prevent this on a PR level, we check for every pull request, if the build is still possible.

Description

This PR introduces the use of FVM. FVM allows to us have a SOT of our Flutter version. Therefore, it's easier to keep the same Flutter version across different developers. Additionally, we can use in CI/CD the same Flutter version in every workflow.

Additional setup

The use of FVM require additionally setup steps for a new developer:

# Install FVM
dart pub global activate fvm

# Install Flutter version
fvm install

How to change the Flutter version

1. Change the version in .fvm/fvm_config.json
2. Run fvm install

Related Tickets

Closes #144

Description

This PR introduces the first integration test. It's a simple one: Sign in with the email address and the password. The main focus of the PR was to set up the integration and fix the errors. Therefore, we can add more integration tests in different PRs.

Demo

https://user-images.githubusercontent.com/24459435/167846068-8747bed6-f775-41f5-8703-c7e3a53a40ec.mov

How to run the integration tests

flutter test \
  integration_test \
  --flavor dev \
  --dart-define \
  USER_1_EMAIL="[email protected]" \
  --dart-define \
  USER_1_PASSWORD="YOUR_PASSWORD"

Native setup for integration tests

I skipped the steps for setting up the iOS and Android device tests, because I think we only need these setups when run our tests with Firebase Test Lab or similar services. Firebase Test Lab needs these steps to properly run the tests. But at the moment, we just run our integration tests with flutter test in emulators/simulators.

Related Tickets

Closes #180

Describe the bug

The Material Icons are looking weird / wrong on alpha web app.

Steps to Reproduce

1. Go to https://alpha.web.sharezone.net
2. Login
3. Click trough app

Current broken behavior

Expected behavior

See Android / iOS app (I'm now too lazy to make the screenshots in the android / ios app 😅)

Screenshots, videos or logs

See broken behavior

Tested device

• Device: MacBook Pro M1
• Browser: Chrome 95.0.4638.69
• OS: macOS 12.0.1
• App version: 1.6.1 (Alpha Web-App)

Additional context

Possible solution

Description

Finding pull requests with GitHub can be hard. Especially when our app has a bug and we try to find the pull request which caused the bug, might it be helpful to labels, like platform: android when we know it something with the Android build or changes to our CI/CD with the label ci/cd.

Therefore, I added the labeler Action to automatically add labels to our pull requests based on the changed file paths.

I just saw that we had a app/coverage folder. I think this was a mistake to commit this folder. So I added coverage/ to the top level .gitignore. Maybe Flutter also adds the coverage as default to the .gitignore file: https://github.com/flutter/flutter/issues/101349.

Description

I'm sure that the jitsi_meet package is the reason why the iOS build is failing in #153. The problem is that the jitsi_meet package isn't maintained anymore. So it's difficult to find a fix so that #153 can be merged.

There are also several issues that Android 12 is not supported anymore by the package (https://github.com/gunschu/jitsi_meet/issues/376, https://github.com/gunschu/jitsi_meet/issues/368, https://github.com/gunschu/jitsi_meet/issues/366).

There is a folk of jitsi_meet called jitsi_meet_wrapper which has better code and is maintained. So I migrated to this package (thanks to @saibotma 💙).

One big disadvantage: jitsi_meet_wrapper uses the current Jitsi iOS SDK which requires +12.0. This means we need to drop the support for iOS 11.0 (other option would be to remove the Jitsi Feature for all users) 😞

Demo

| iOS | Android | |-|-| | | |

ToDo

• [x] Run on Android emulator

Create sz cli commands that:

• Check that all files have the correct licence headers
• Add licence header to all files that do not yet have to correct header

Moved most of the holiday code to lib/holidays.
I left holidays_bloc inside of the app code since it interacts with the UserGateway and is more specific to the dashboard page widget. I didn't change any logic.
I ran the app manually on the mac to check if it still works.

Description

I'm creating a lot of homework for myself (not official homework, just small homework for myself, like to look up the word XZY) to a course. These homework should not be shared with course because they specific for me.

Having an option in the settings to say that I'm adding homework by default as private, would be helpful. This option would count for every course (I think per course setting would way to overkill).

Problem

For some homework, you are working in groups (e.g. with 3 other students). Currently, it's not possible to create a homework just for these users. You can either add the homework for your own or for the whole course.

Idea

An option to make the homework private for a selection of users.

Edge Cases

When changing the course while adding a homework, we should reset the selection of users because there could be users that are not in the new selected course.