Skip to content

chore: update example demo to be similar to other sdks#852

Open
fadi-george wants to merge 49 commits intomainfrom
fg/unity-new-demo
Open

chore: update example demo to be similar to other sdks#852
fadi-george wants to merge 49 commits intomainfrom
fg/unity-new-demo

Conversation

@fadi-george
Copy link
Collaborator

@fadi-george fadi-george commented Feb 25, 2026

Description

One Line Summary

Brings the unity example demo to be more like the other sdk projects

Screenshot 2026-02-24 at 10 23 14 PM Screenshot 2026-02-24 at 10 23 21 PM Screenshot 2026-02-24 at 10 23 26 PM

Details

  • Added styles.md to sdk-shared and applied to the unity demo
  • Removed unnecessary _project.SetBuildProperty(extensionGuid, "ARCHS", "arm64"); in ios BuildPostProcessor . Verified by testing both simulator and physical devices
  • Adds AddLocationUsageDescription in ios BuildPostProcessor to help with location prompt otherwise it wont work

Motivation

Want to have consistent demo apps for each sdk

Testing

  • Tested on both android and ios emulators

Affected code checklist

  • Notifications
    • Display
    • Open
    • Push Processing
    • Confirm Deliveries
  • Outcomes
  • Sessions
  • In-App Messaging
  • REST API requests
  • Public API changes

Checklist

Overview

  • I have filled out all REQUIRED sections above
  • PR does one thing
    • If it is hard to explain how any codes changes are related to each other then it most likely needs to be more than one PR
  • Any Public API changes are explained in the PR details and conform to existing APIs

Testing

  • I have included test coverage for these changes, or explained why they are not needed
  • All automated tests pass, or I explained why that is not possible
  • I have personally tested this on my device, or explained why that is not possible

Final pass

  • Code is as readable as possible.
    • Simplify with less code, followed by splitting up code into well named functions and variables, followed by adding comments to the code.
  • I have reviewed this PR myself, ensuring it meets each checklist item
    • WIP (Work In Progress) is ok, but explain what is still in progress and what you would like feedback on. Start the PR title with "WIP" to indicate this.

This change is Reviewable

@fadi-george fadi-george requested a review from a team February 25, 2026 06:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants