@nativescript/android
Advanced tools
Contains the source code for the NativeScript's Android Runtime. NativeScript is a framework which enables developers to write truly native mobile applications for Android and iOS using JavaScript and CSS. Each mobile platform has its own ecosystem and offers completely different development tools and language(s) - Java for Android and Objective C (Swift) for iOS. In order to translate JavaScript code to the corresponding native APIs some kind of proxy mechanism is needed. This is exactly what the "Runtime" parts of NativeScript are responsible for. The Android Runtime may be thought of as "The Bridge" between the JavaScript and Android worlds. A NativeScript application for Android is a standard native package (apk) which besides the JavaScript files embed the runtime as well.
Several Wiki pages describe some internal topics about the runtime here
The repo is structured in the following projects (ordered by dependencies):
extend routine.The NativeScript Android Runtime architecture can be summarized in the following diagram.
For more details on how it works, read the documentation.
Following are the minimal prerequisites to build the runtime package.
git clone --recurse-submodules git@github.com:NativeScript/android-runtime.gitNote: You might need to run the Android Studio from the command line in order to preserve the environment variables. This is in case you get errors like "missing npm" if starting the studio the usual way.
Install dependencies from NPM:
cd test-app/build-tools/jsparser
npm install
Set environment variables:
JAVA_HOME such that $JAVA_HOME/bin/java points to your Java executableANDROID_HOME pointing to where you have installed the Android SDKANDROID_NDK_HOME pointing to the version of the Android NDK needed for this version of NativeScriptRun command
Windows:
gradlew
Mac/Linux:
./gradlew
The build process includes building of the runtime package (both optimized and with unstripped v8 symbol table), as well as all supplementary tools used for the android builds: metadata-generator, binding-generator, metadata-generator, static-binding-generator
The result of the build will be in the dist folder.
Note: To cut the build time in half and package only the optimized (stripped) version of the runtime package comment out 'tasks.generateRuntimeAar.execute()' in the build.gradle script.
Go to subfolder test-app after you built the runtime.
Start an emulator or connect a device.
Note: Keep in mind the device or emulator needs to have an sdcard mounted.
Run command
gradlew runtests
cd test-app
npm install
npx ns debug android --start
(If you instead have the nativescript NPM module installed globally,
you can omit the npm install and the npx prefix.)
devtools://devtools/bundled/inspector.html?ws=localhost:40000.
Open this URL in Chrome or Chromium.We love PRs! Check out the contributing guidelines. If you want to contribute, but you are not sure where to start - look for issues labeled help wanted.
Please, use github issues strictly for reporting bugs or requesting features. For general questions and support, check out Stack Overflow or ask our experts in NativeScript community Slack channel.
8.5.1 (2023-07-24)
Avoid setting the same property on an ObjectTemplate twice (9e610c8)
Don't access super property on implementation object (d8b8bc0)
Don't iterate properties in GetImplementedInterfaces (9dfae65)
intermediary fix for https://github.com/NativeScript/android/pull/1771 (32c7abb)
Leave context after Runtime::PrepareV8Runtime() (cd1d285)
memory leak on accessing static interface methods (88ce2d8)
memory leak on saving code cache (6d416a1)
Update common-runtime-tests-app (c8db3ca)
update legacy android version in package.json (#1744) (b4ad8e5)
Use Isolate::TryGetCurrent() (afe026a)
Remove weak callback from __postFrameCallback cache (#1755) (ff1b979), closes #1755
The NDK profiler was not functional, since nothing in the build process defined the NDK_PROFILER_ENABLED preprocessor symbol. The start and stop functions were already no-ops.
RunMicrotasks no longer exists, it's already been replaced in the code with PerformMicrotaskCheckpoint.
V8 doc: https://docs.google.com/document/d/1sTc_jRL87Fu175Holm5SV0kajkseGl2r8ifGY76G35k/edit
The V8 usage examples show unique_ptr here; it probably doesn't matter much, but we don't need the backing store after creating the ArrayBuffer, and I believe shared_ptr is slightly more overhead than unique_ptr.
For convenience, replace the manual empty deleter for direct buffers with v8::BackingStore::EmptyDeleter.
Weak finalizer callbacks are going away in V8 11.x, so we have to remove this one. Luckily, a finalizer callback is not necessary - it's never needed to prevent the frame callback from being collected.
However, a weak callback is not necessary in the first place. We can just clean up the cache entry after the callback is executed, since it is only executed once.
Note that the call to erase() destructs the FrameCallbackCacheEntry
instance, making entry a dangling pointer, so don't use it after the
erase(). There's probably a safer way to do this, although the way that
first occurred to me (pass the key to the callback instead of the entry,
and then use std::unordered_map::extract()) is not available on
robin_hood::unordered_map.
There was a bug where __postFrameCallback() would not always cause the
callback to be called. Without initializing removed, sometimes it would
have a nonzero value, so the callback would be ignored.
Clearing the persistent handles in the destructor makes it a bit easier to deal with the cache entry's lifetime: they are cleared whenever the entry is removed from the cache.
We do this for both the main thread callback cache and the frame callback cache.
Adding a destructor makes the cache entries non-movable. But the only place where they were moved was when inserting them into the cache anyway. We can use C++17's try_emplace() method to insert them without having to move them.
This avoids the situation of forgetting to add an ID to the cache entry.
This fixes a few places where we can avoid double lookups:
In RunOnMainThreadFdCallback, we already have a valid iterator, so no need to look up the same key again in RemoveKey (this is the only usage of RemoveKey, so we can remove it.) (Additionally, we probably want to remove the cache entry before throwing a NativeScript exception.)
In PostFrameCallback and RemoveFrameCallback, we should not do contains() immediately followed by find().
chore: Fix runtime typo
chore: Ignore main thread and frame callback return values
We don't do anything with the return value from these callbacks, so it's OK to ignore them and not convert them to a local handle.
FAQs
NativeScript for Android using v8
The npm package @nativescript/android receives a total of 1,919 weekly downloads. As such, @nativescript/android popularity was classified as popular.
We found that @nativescript/android demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 0 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Research
Security News
Socket researchers have discovered multiple malicious npm packages targeting Solana private keys, abusing Gmail to exfiltrate the data and drain Solana wallets.
Security News
PEP 770 proposes adding SBOM support to Python packages to improve transparency and catch hidden non-Python dependencies that security tools often miss.
Security News
Socket CEO Feross Aboukhadijeh discusses open source security challenges, including zero-day attacks and supply chain risks, on the Cyber Security Council podcast.