mirror of https://github.com/flutter/samples.git synced 2025-11-08 13:58:47 +00:00

Files

dependabot[bot] d97d813a94 Bump jnigen from 0.8.0 to 0.9.0 in /experimental/pedometer (#2269 )

Bumps [jnigen](https://github.com/dart-lang/native/tree/main/pkgs) from 0.8.0 to 0.9.0.
<details>
<summary>Commits</summary>
<ul>
<li>See full diff in <a href="https://github.com/dart-lang/native/commits/HEAD/pkgs">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=jnigen&package-manager=pub&previous-version=0.8.0&new-version=0.9.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.

---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge and block automerging
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

2024-05-03 06:39:14 +00:00

android

Pedometer dependency updates and regeneration (#2133 )

2024-01-05 20:48:39 +10:00

example

Update pedometer sample for jni 0.8.0 (#2237 )

2024-04-09 12:55:27 -05:00

ios

Pedometer dependency updates and regeneration (#2133 )

2024-01-05 20:48:39 +10:00

lib

Update pedometer sample for jni 0.8.0 (#2237 )

2024-04-09 12:55:27 -05:00

src

Update pedometer sample for jni 0.8.0 (#2237 )

2024-04-09 12:55:27 -05:00

.gitignore

Add experimental/pedometer (#1587 )

2023-01-24 10:31:12 +10:00

.metadata

[experimental/pedometer] Use jnigen and jni version from pub instead of git url. (#1655 )

2023-02-20 10:56:12 +01:00

analysis_options.yaml

Add experimental/pedometer (#1587 )

2023-01-24 10:31:12 +10:00

CHANGELOG.md

Add experimental/pedometer (#1587 )

2023-01-24 10:31:12 +10:00

ffigen.yaml

Simplify experimental pedometer example (#2104 )

2023-12-06 18:58:58 +10:00

jnigen.yaml

[experimental/pedometer] Update jni and jnigen to 0.6 (#2006 )

2023-09-02 07:26:40 +10:00

LICENSE

Add experimental/pedometer (#1587 )

2023-01-24 10:31:12 +10:00

pubspec.yaml

Bump jnigen from 0.8.0 to 0.9.0 in /experimental/pedometer (#2269 )

2024-05-03 06:39:14 +00:00

README.md

Pedometer dependency updates and regeneration (#2133 )

2024-01-05 20:48:39 +10:00

README.md

FFIgen + JNIgen pedometer

This is a demo for some of our tooling around calling platform APIs directly from dart code. This repository represents a demo of a plugin that leverages FFIgen & JNIgen. There is also an example pedometer app that uses the bindings generated from these tools.

FFIgen is used to generate bindings for C, Objective-C and Swift APIs.
JNIgen is used to generate bindings for Java and Kotlin APIs.

These tools are both experimental and are currently a work in progress. If you find any issues or have feedback, please file it on the corresponding GitHub repositories.

Re-generating bindings

The bindings that allow the Dart code to call the platform code have already been generated in the \lib folder. You can regenerate them by following the steps below:

FFIgen

Configuration of FFIgen for the CoreMotion framework is in the ffigen.yaml file. FFIgen currently does not support autogenerating code to handle callbacks. So, there are a few extra steps needed to appropriately handle callbacks in Objective-C. You can read more about this limitation on dart.dev.

dart run ffigen --config ffigen.yaml

JNIgen

Configuration of JNIgen for the HealthConnect API is in the jnigen.yaml file.

Build an Android APK file from the example app. Currently, JNIgen requires at least one APK build to obtain the classpaths of Android Gradle libraries.
```
cd example && flutter build apk
```

Return to the /pedometer directory and run jnigen:

cd .. && dart run jnigen --config jnigen.yaml

Running the example app

The example app is located in the /example directory, and the following commands assume they are being run from that location.

Note that step counting is only available on physical devices.

iOS

Run flutter run and choose your physical device.
Allow the pedometer app access to step counting.

Android

Make sure that Google Fit is installed (to ensure that steps are being counted).
Run flutter run and choose your physical device.
Install Health Connect and grant access to Google Fit and the jni_demo app.

Project structure

src: Contains the native source code, and a CMakeLists.txt file for building that source code into a dynamic library.
lib: Contains the Dart code that defines the API of the plugin and calls into the native code using dart:ffi.
platform folders (ios etc.): Contain the build files for building and bundling the native code library with the platform application.
example: Contains the native source code for building that source code into a dynamic library.