Gathering detailed insights and metrics for com.onesignal.unity.core
Gathering detailed insights and metrics for com.onesignal.unity.core
Gathering detailed insights and metrics for com.onesignal.unity.core
Gathering detailed insights and metrics for com.onesignal.unity.core
npm install com.onesignal.unity.core
72.5
Supply Chain
37.8
Quality
94.2
Maintenance
100
Vulnerability
87.3
License
Module System
Unable to determine the module system for this package.
Min. Node Version
Typescript Support
Node Version
NPM Version
222 Stars
1,428 Commits
61 Forks
54 Watching
19 Branches
23 Contributors
Updated on 27 Nov 2024
C# (88.84%)
Objective-C++ (8%)
Shell (1.81%)
Swift (0.78%)
Objective-C (0.58%)
Cumulative downloads
Total Downloads
Last day
-63.3%
453
Compared to previous day
Last week
-17.5%
6,286
Compared to previous week
Last month
1.4%
31,948
Compared to previous month
Last year
72%
392,209
Compared to previous year
Our new user-centric APIs and v5.x.x SDKs offer an improved user and data management experience. However, they may not be at 1:1 feature parity with our previous versions yet.
If you are migrating an existing app, we suggest using iOS and Android’s Phased Rollout capabilities to ensure that there are no unexpected issues or edge cases. Here is the documentation for each:
If you run into any challenges or have concerns, please contact our support team at support@onesignal.com
A free email, sms, push notification and in app messaging solution for mobile applications built through Unity.
OneSignal provides a fully array of omni-channel messaging solutions across:
And via many additional platforms. Check them all out!
You must generate the appropriate credentials for the platform(s) you are releasing on:
There are two methods of installation available for the OneSignal Unity SDK:
Upgrading from 2.x.x to 3.x.x?
Please check out our v2 to v3 migration guide.
Upgrading from 3.x.x to 5.x.x?
Please check out our v3 to v5 migration guide.
Add the OneSignal Unity SDK as an available asset to your account by clicking Add to My Assets from our listing on the Unity Asset Store.
Find the package waiting for you to download by clicking Open in Unity from that same page. This will open the Unity Editor and its Package Manager window.
On the SDK's listing in the Editor click the Download button. When it finishes click Import.
A prompt to import all of the files of the OneSignal Unity SDK will appear. Click Import to continue and compile the scripts into your project.
Navigate to Window > OneSignal SDK Setup (or follow the popup if upgrading) in the Unity Editor which will bring up a window with some final steps which need to be completed in order to finalize the installation. The most important of these steps is Import OneSignal packages.
Depending on your project configuration and if you are upgrading from a previous version, some of these steps may already be marked as "completed"
After importing the packages Unity will notify you that a new registry has been added and the OneSignal SDK Setup window will have refreshed with a few additional steps. Following these will finalize your installation of the OneSignal Unity SDK.
From within the Unity Editor navigate to Edit > Project Settings and then to the Package Manager settings tab.
Create a New Scoped Registry by entering
Name npmjs
URL https://registry.npmjs.org
Scope(s) com.onesignal
and click Save.
Open the Window > Package Manager and switch to My Registries via the Packages: dropdown menu. You will see all of the OneSignal Unity SDK packages available on which you can then click Install for the platforms you would like to include. Dependencies will be added automatically.
Once the packages have finished importing you will find a new menu under Window > OneSignal SDK Setup. Open it and you will find some final steps which need to be completed in order to finalize the installation.
Depending on your project configuration and if you are upgrading from a previous version, some of these steps may already be marked as "completed"
After building in Unity and exporting the XCode project follow these steps:
To open your project ensure that you use the .xcworkspace
file and not the .xcodeproj
to open the project.
Click on the Unity-iPhone project and its similarly named target and select the Signing & Capabilities tab.
From here check Automatically manage signing, on the prompt click Enable Automatic, and select your Team.
Scroll down to App Groups and click on the refresh button.
NOTE: You may have to press this a few times as it will ask you for each signing type.
Repeat the same steps above but for the OneSignalNotificationServiceExtension target this time.
App Groups should now be provisioned for you going forward for your iOS bundle id, even on clean builds.
Make sure all Targets have Enable Bitcode set to No in Build Settings.
Most of the Android setup was already handled during installation!
The only thing remaining is to setup your own notification icons. You can do this be replacing the example icons located at Assets/Plugins/Android/OneSignalConfig.androidlib/src/main/res
with your own. There is a complete guide for this in the plugin's README. See our
Customize Notification Icons page for additional details.
You can find a complete implementation in our included example MonoBehaviour. Additionally we have included a sample scene which you can run to test out the SDK.
Located in the com.onesignal.unity.core
package we've include a simple prefab which initializes OneSignal. You can easily find it using the Asset search bar
to find OneSignalController.prefab
and making sure to select All or In Packages for your search option. Drag the prefab into your very first scene, fill
in the App Id, and you are immediately ready to go!
To get started add the following code in an appropriate place such as the Start
method of a MonoBehaviour
early in your application's lifecycle.
1// Replace 'YOUR_ONESIGNAL_APP_ID' with your OneSignal App ID from app.onesignal.com 2OneSignal.Initialize("YOUR_ONESIGNAL_APP_ID");
You are now ready to start sending and receiving notifications and in-app messages. For additional information please see our complete OneSignal Unity SDK docs.
See OneSignal's OneSignal SDK Reference page for a list of all available methods.
See this repository's releases for a complete change log of every released version.
Please visit this repository's Github issue tracker for feature requests and bug reports related specifically to the SDK.
For account issues and support please contact OneSignal support from the OneSignal dashboard.
No vulnerabilities found.
Reason
all changesets reviewed
Reason
14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Reason
no dangerous workflow patterns detected
Reason
0 existing vulnerabilities detected
Reason
license file detected
Details
Reason
binaries present in source code
Details
Reason
detected GitHub workflow tokens with excessive permissions
Details
Reason
no effort to earn an OpenSSF best practices badge detected
Reason
dependency not pinned by hash detected -- score normalized to 0
Details
Reason
project is not fuzzed
Details
Reason
Project has not signed or included provenance with any releases.
Details
Reason
security policy file not detected
Details
Reason
SAST tool is not run on all commits -- score normalized to 0
Details
Score
Last Scanned on 2024-11-25
The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.
Learn More