You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you are working on a fork of this repository and want to resolve NuGet packages published from your fork, run:
19
+
If you are working from a fork and need to restore packages published from that fork, configure a GitHub Packages source:
20
20
21
21
```sh
22
-
# Using GitHub CLI (recommended)
23
22
./scripts/configure-github-feed.sh --gh
23
+
```
24
+
25
+
You can also use a local personal access token with `read:packages` scope:
24
26
25
-
# Or using a personal access token
27
+
```sh
26
28
export GITHUB_PACKAGES_PAT="your_github_pat_here"
27
29
./scripts/configure-github-feed.sh
28
30
```
29
31
30
-
This script:
31
-
- Auto-detects your fork owner from the git remote URL
32
-
- Configures a GitHub Packages feed (`github-<YourUsername>`)
33
-
- Allows `dotnet restore` to resolve packages published from your fork
32
+
Do not commit tokens or generated local NuGet credentials.
34
33
35
-
**Note**: Your GitHub Personal Access Token must have the `read:packages` scope. See [GitHub docs](https://docs.github.com/en/authentication/keeping-your-account-and-data-secure/managing-your-personal-access-tokens#creating-a-personal-access-token-classic) for token creation.
34
+
The script detects the fork owner from the git remote, adds a source named like `github-<YourUsername>`, and allows `dotnet restore` to resolve fork-published packages.
36
35
37
-
## Build + pack a component
36
+
## Build and Pack One Component
38
37
39
-
Build and produce `.nupkg` files into`./output`:
38
+
Build and produce `.nupkg` files under`./output`:
40
39
41
40
```sh
42
41
dotnet tool run dotnet-cake -- --target=nuget --names=Google.SignIn
43
42
```
44
43
45
-
## Clean-up
46
-
47
-
To clean generated folders:
44
+
## Clean Generated Output
48
45
49
46
```sh
50
47
dotnet tool run dotnet-cake -- --target=clean
@@ -54,34 +51,30 @@ dotnet tool run dotnet-cake -- --target=clean
54
51
55
52
### MSB4057: The target "source/..." does not exist
56
53
57
-
This error can occur when using MSBuild solution-level targets with certain .NET SDK versions. The `build.cake` script avoids this by building each `.csproj` directly in dependency order, which is more explicit and reliable.
54
+
This can happen when using MSBuild solution-level targets with some .NET SDK versions. The Cake script builds `.csproj`files directly in dependency order to avoid that failure mode.
58
55
59
56
### NU1101: Unable to find package AdamE.Google.iOS.AppCheckCore
60
57
61
-
Some packages (like `SignIn`) depend on `AppCheckCore` which is built from this repo. The Cake script handles this automatically by building dependencies first. If you still encounter this:
58
+
Some packages depend on other packages built from this repository. The Cake script handles dependency-first packing. If restore still fails, run the component build through Cake instead of building the project directly:
62
59
63
-
1. Ensure you're using the latest `build.cake` (it should iterate `ARTIFACTS_TO_BUILD`)
64
-
2. Run the full build: `dotnet tool run dotnet-cake -- --target=nuget --names=Google.SignIn`
60
+
```sh
61
+
dotnet tool run dotnet-cake -- --target=nuget --names=Google.SignIn
62
+
```
65
63
66
64
### Code signing errors during xcframework build
67
65
68
-
The Cake scripts disable code signing by default (`CODE_SIGNING_ALLOWED=NO`) for CI compatibility. If you need signed frameworks, override the build settings in `common.cake`.
66
+
The Cake scripts disable code signing by default (`CODE_SIGNING_ALLOWED=NO`) for CI compatibility. If you need signed frameworks, override the build settings locally instead of committing signing material.
69
67
70
68
### NuGet feed issues
71
69
72
-
If you see errors like:
73
-
```
74
-
NU1101: Unable to find package AdamE.Firebase.iOS.AppCheck [...]
75
-
```
70
+
If restore cannot find packages from a fork, verify the configured sources:
76
71
77
-
This may occur if your GitHub Packages feed is not configured. See "[Configure GitHub Packages feed](#configure-github-packages-feed-for-fork-contributors)" above.
Firebase Analytics is a free app measurement solution that provides insight on app usage and user engagement.
1
+
# Firebase Analytics
2
2
3
-
At the heart of Firebase is Firebase Analytics, a free and unlimited analytics solution. Analytics integrates across Firebase features and provides you with unlimited reporting for up to 500 distinct events that you can define using the Firebase SDK. Analytics reports help you understand clearly how your users behave, which enables you to make informed decisions regarding app marketing and performance optimizations.
3
+
This path is retained for existing links, but this repository does not maintain a copied Firebase Analytics walkthrough.
4
4
5
-
## Key capabilities
5
+
These packages are thin .NET bindings over the native Firebase Apple SDKs. Use the official native documentation as the source of truth for setup, product behavior, console workflows, quotas, policy requirements, and examples.
6
6
7
-
|||
8
-
|-:|-|
9
-
|**Unlimited Reporting:**| Firebase Analytics provides unlimited reporting on up to 500 distinct events. |
10
-
|**Audience Segmentation:**| Custom audiences can be defined in the Firebase console based on device data, custom events, or user properties. These audiences can be used with other Firebase features when targeting new features or notifications messages. |
7
+
## Native Documentation
11
8
12
-
## How does it work?
9
+
- Firebase Apple setup: https://firebase.google.com/docs/ios/setup
Firebase Analytics helps you understand how people use your iOS app. The SDK automatically captures a number of events and user properties and also allows you to define your own custom events to measure the things that uniquely matter to your business. Once the data is captured, it's available in a dashboard through the Firebase console. This dashboard provides detailed insights about your data — from summary data such as active users and demographics, to more detailed data such as identifying your most purchased items.
12
+
## Binding Package
15
13
16
-
Analytics also integrates with a number of other Firebase features. For example, it automatically logs events that correspond to notification messages sent via the Notifications composer and provides reporting on the impact of each campaign.
Firebase Analytics helps you understand how your users behave, so you can make informed decisions about how to market your app. See the performance of your campaigns across organic and paid channels to understand which methods are most effective at driving high-value users. If you need to perform custom analysis or join your data with other sources you can link your Analytics data to BigQuery, which allows for more complex analysis like querying large data sets and joining multiple data sources.
19
-
20
-
<sub>_Portions of this page are modifications based on work created and [shared by Google](https://developers.google.com/readme/policies/) and used according to terms described in the [Creative Commons 3.0 Attribution License](http://creativecommons.org/licenses/by/3.0/). Click [here](https://firebase.google.com/docs/analytics/) to see original Firebase documentation._</sub>
18
+
Document only binding-specific caveats in this repository. Product usage guidance belongs in the official native docs.
0 commit comments