Git Product home page Git Product logo

maker-starter-app's Introduction

Maker Starter App

Getting Started

App Setup

  1. First add your environment variables. See the installing section below for more detail on how to do so.
    1. You will need a Mapbox API key to show the map for Hotspot onboarding.
    2. You will need a Google API key for address and location search.
  2. Rename your application using React Native Rename. You will want to pass in the custom bundle identifier for Android and also change it manually for iOS.
  3. Update your theme colors in theme.ts. The theme controls the look of the application.
  4. Add your Hotspot and Antenna data in the makers folder. See the Makers README for more detail.
  5. You will need to update your App Scheme for any deep linking. There are guides for both iOS and Android.
  6. The basics of the Helium React Native SDK and Helium Blockchain API have been integrated into this starter app. Review the docs to learn more.

React Native Dev Setup

If you have already set up react native on your machine, skip to the installing section.

React Native dependencies

You will need Node, Watchman, Yarn, the React Native command line interface, Android Studio, and Xcode.

While you can use any editor of your choice to develop your app, you will need to install Xcode and Android Studio in order to set up the necessary tooling to build your React Native app for iOS and Android.

A good free editor is Visual Studio Code.

Node, Watchman, Yarn

We recommend installing Node, Yarn, and Watchman using Homebrew. Run the following commands in a Terminal after installing Homebrew:

brew install node
brew install watchman
brew install yarn

If you have already installed Node on your system, make sure it is up to date with the LTS version.

Watchman is a tool by Facebook for watching changes in the filesystem. It is highly recommended you install it for better performance.

The React Native CLI

Node comes with npm, which lets you install the React Native command line interface.

Run the following command in a Terminal:

npm install -g react-native-cli

If you get an error like Cannot find module 'npmlog', try installing npm directly:

curl -0 -L https://npmjs.org/install.sh | sudo sh.

Xcode

The easiest way to install Xcode is via the Mac App Store. Installing Xcode will also install the iOS Simulator and all the necessary tools to build your iOS app.

If you have already installed Xcode on your system, make sure it is up to date.

Command Line Tools

You will also need to install the Xcode Command Line Tools. Open Xcode, then choose "Preferences..." from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown.

Java Development Kit

React Native requires the Java SE Development Kit (JDK). Download and install JDK 8 if needed.

Android development environment

Setting up your development environment can be somewhat tedious if you're new to Android development. If you're already familiar with Android development, there are a few things you may need to configure. In either case, please make sure to carefully follow the next few steps.

1. Install Android Studio

Download and install Android Studio. Choose a "Custom" setup when prompted to select an installation type. Make sure the boxes next to all of the following are checked:

  • Android SDK
  • Android SDK Platform
  • Performance (Intel ® HAXM)
  • Android Virtual Device

Then, click "Next" to install all of these components.

If the checkboxes are grayed out, you will have a chance to install these components later on. Once setup has finalized and you're presented with the Welcome screen, proceed to the next step.

2. Install the Android SDK

Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the Android 28 SDK in particular. Additional Android SDKs can be installed through the SDK Manager in Android Studio.

The SDK Manager can be accessed from the "Welcome to Android Studio" screen. Click on "Configure", then select "SDK Manager".

Select the "SDK Platforms" tab from within the SDK Manager, then check the box next to "Show Package Details" in the bottom right corner. Look for and expand the Android 28 entry, then make sure the following items are all checked:

  • Google APIs
  • Android SDK Platform 28
  • Intel x86 Atom_64 System Image
  • Google APIs Intel x86 Atom_64 System Image

Next, select the "SDK Tools" tab and check the box next to "Show Package Details" here as well. Look for and expand the "Android SDK Build-Tools" entry, then make sure that 30-rc1, 29.0.3, and 28.0.3 are selected.

Finally, click "Apply" to download and install the Android SDK and related build tools.

3. Configure the ANDROID_HOME environment variable

The React Native tools require some environment variables to be set up in order to build apps with native code.

Add the following lines to your $HOME/.bash_profile config file:

export ANDROID_HOME=$HOME/Library/Android/sdk
export PATH=$PATH:$ANDROID_HOME/tools
export PATH=$PATH:$ANDROID_HOME/platform-tools

Installing

Environment Variables

  1. Copy the file .env.sample and rename it to .env.
  2. Once renamed update the values within the file.
  3. In order for maps to load you will need to create your own Mapbox access token.

Dependencies

Install 3rd party dependencies

yarn install

You also need cocoapods for iOS

sudo gem install cocoapods

Then install the pods for iOS (Not needed for Android)

yarn pod-install

If the app is not working you may want to clean your workspace and then follow the running the app section below

yarn clean-install
yarn clean-start

Running The App

iOS

The fastest way to run the app is on the iOS simulator. Just type:

yarn ios

You can also open the MakerApp.xcworkspace file in the /ios folder using xcode and run the app on your device or any other simulator.

Android

Similar to iOS, run

yarn android

You can also open the Android project in Android Studio by selecting open an existing project and selecting the /android folder.

maker-starter-app's People

Contributors

matthewcarlreetz avatar tyler-whitman avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

maker-starter-app's Issues

helium/maker-starter-appfo yarn install error in windows10

I cloned the open source code of helium/maker-starter-appfor local runtime. When I install the dependencies using yarn install I get the following error.Have you ever encountered such a problem? Can you give me any tips on what I need to do? Thank you very much.

yarn install v1.22.5
[1/4] Resolving packages...
[2/4] Fetching packages...
info [email protected]: The platform "win32" is incompatible with this module.
info "[email protected]" is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning " > @helium/[email protected]" has incorrect peer dependency "@helium/crypto-react-native@^3.9.0".
warning " > @helium/[email protected]" has incorrect peer dependency "@helium/currency@^3.25.1".
warning " > @helium/[email protected]" has incorrect peer dependency "@helium/http@^3.43.0".
warning " > @helium/[email protected]" has incorrect peer dependency "@helium/onboarding@^3.59.0".
warning " > @helium/[email protected]" has incorrect peer dependency "@helium/proto-ble@^3.37.0".
warning " > @helium/[email protected]" has incorrect peer dependency "@helium/transactions@^3.38.0".
warning " > @helium/[email protected]" has unmet peer dependency "events@^3.3.0".
warning " > @helium/[email protected]" has incorrect peer dependency "h3-js@^3.7.2".
warning " > @helium/[email protected]" has incorrect peer dependency "query-string@^7.0.1".
warning " > @helium/[email protected]" has unmet peer dependency "readable-stream@^3.6.0".
warning " > @helium/[email protected]" has unmet peer dependency "stream@^0.0.2".
warning " > @helium/[email protected]" has unmet peer dependency "@helium/crypto@^4.3.1".
warning " > @react-native-mapbox-gl/[email protected]" has unmet peer dependency "prop-types@>=15.5.8".
warning " > @react-native-mapbox-gl/[email protected]" has incorrect peer dependency "react@^16.6.1".
warning " > @react-navigation/[email protected]" has unmet peer dependency "@react-native-community/masked-view@>= 0.1.0".
warning "expo-camera > @koale/[email protected]" has incorrect peer dependency "react@^16.8.0".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
warning "react-native > react-native-codegen > [email protected]" has unmet peer dependency "@babel/preset-env@^7.1.6".
warning " > [email protected]" has incorrect peer dependency "react@^16.8.0".
warning " > [email protected]" has incorrect peer dependency "react-native@^0.59.0".
warning " > [email protected]" has unmet peer dependency "react-native-windows@>=0.61".
warning " > [email protected]" has incorrect peer dependency "react@^16.8.6".
warning " > [email protected]" has unmet peer dependency "react-dom@^16.8.6".
warning " > [email protected]" has incorrect peer dependency "@typescript-eslint/[email protected]".
warning " > [email protected]" has incorrect peer dependency "@typescript-eslint/[email protected]".
warning " > [email protected]" has unmet peer dependency "[email protected]".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
warning " > [email protected]" has unmet peer dependency "[email protected] || 4.x".
warning " > [email protected]" has incorrect peer dependency "[email protected] || 2.x".
warning " > [email protected]" has incorrect peer dependency "[email protected]".
[4/4] Building fresh packages...
[8/8] ⢀ @helium/react-native-sdk
[-/8] ⠠ waiting...
[-/8] ⠠ waiting...
[4/8] ⠠ postinstall-postinstall
error E:\APP\Zakazi\maker-starter-app\node_modules@helium\react-native-sdk: Command failed.
Exit code: 1
Command: rm -rf node_modules
Arguments:
Directory: E:\APP\Zakazi\maker-starter-app\node_modules@helium\react-native-sdk

Allow Makers to deeplink to Helium to sign transactions

For improved security best practices, we should remove the part of the onboarding flow where users enter their 12 words into a maker app, and instead, have the maker app request a helium wallet to sign transactions with the user's private key.

The onboarding flow for the maker app would start with linking a wallet address with the maker app with CTA to link from a supported Helium wallet app, or download a supported Helium wallet app.

Users will be asked to approve/link to the maker app from a Helium wallet app. The two apps are now linked together and can sign transactions on behalf of the maker app.

Transactions we'll support in this starter app:
add_gateway
transfer_hotspot_v2
assert_location

Example flow (once linked):
user adds a Hotspot (maker app) > partial transaction deep linked to Helium app > user confirms transaction on Helium app > passes back partial transaction back to maker app > maker app submits transaction to the blockchain using the maker's desired API endpoint, hitting their desired onboarding server.

user updates a Hotspot location (maker app) > partial transaction deep linked to Helium app > user confirms transaction on Helium app > passes back partial transaction back to maker app > maker app submits transaction to the blockchain using the maker's desired API endpoint

User imitates transfer_hotspot_v2 transaction (maker app) > partial transaction deep linked to Helium app > user confirms transaction on Helium app > passes back partial transaction back to maker app > maker app submits transaction to the blockchain using the maker's desired API endpoint

TypeErrors & Unhandled Promises, when registering a transaction | (evaluating '_ref3.success') & (evaluating 'createTxns.data')

Hello,

I would like to ask for guidance on how can I solve the problems mentioned below.

Setup:

  1. I have set up a Solana RPC endpoint and I am on cluster devnet, tried on testnet as well.
  2. I use the onboarding maker address provided in the migration guide.
  3. Dependencies
    "@helium/address": "^4.8.1",
    "@helium/crypto-react-native": "^4.8.1",
    "@helium/currency": "^4.10.0",
    "@helium/currency-utils": "^0.0.49",
    "@helium/http": "^4.10.0",
    "@helium/onboarding": "^4.10.0",
    "@helium/proto-ble": "^4.8.1",
    "@helium/react-native-sdk": "^2.0.18",
    "@helium/transactions": "^4.8.1",
    "@helium/wallet-link": "^4.10.0",

Problems:

  1. When I scan the QR code of my hotspot or set up the location I get this error:

[TypeError: undefined is not an object (evaluating '_ref3.success')]

  1. When I click Register Hotspot

Possible Unhandled Promise Rejection (id: 0): TypeError: undefined is not an object (evaluating 'createTxns.data')

And the hotspot is not registered, it doesn't even redirect me to the wallet as it did.
Also, I don't know where to look for the failed pending transactions.
Before it was this place: Failed Pending Transactions
But now where I can look for them?
Additionally, I can see some failed pending transactions on this old place.

Thank you for your time!

Kind regards!

Runtime error when opening page HotspotSetupExternalScreen.tsx (add an hotspot with QR onboarding)

I think this error can occur to everyone with the default code, but tell me if this doesn't happen to you, maybe it's my fault.
The app compiles normally, I open the app, tap on Add hotspot, tap on Example QR Hotspot, the error occurs. The app crashes and the error was something like "undefined is not a function".
So I checked the code with VSCode and in /maker-starter-app/src/features/hotspots/setup/HotspotSetupExternalScreen.tsx in line 8 there's the import of usePermissions from expo-barcode-scanner. Here VSCode says that the library doesn't have any export of usePermissions. I checked the code of expo-barcode-scanner and I see that usePermissions is defined inside BarCodeScanner which the app already imports.
So I fixed the error by commenting the import of usePermissions and in line 40 I added "BarCodeScanner." before usePermissions.
This is the resulting code after my edits:

import {
  BarCodeScanner,
  BarCodeScannerResult,
  // usePermissions,
} from 'expo-barcode-scanner'

...

const [perms] = BarCodeScanner.usePermissions({
    request: true,
  })

This fixed the error, so now when I tap on Example QR Hotspot the app asks the permissions correctly and then shows the expected page.

Please let me know if this is a common problem and if you are going to include this fix. Thanks

Android build error: Execution failed for task ':helium_react-native-sdk:compileDebugKotlin'.

Up to a month ago I could build my android app, but since two weeks ago I get this error without editing anything in my project.
I also just tried to build the app from your current github project and I still get the error.
I'm using ubuntu terminal to build the app.

Steps to reproduce the error:

  1. Clone the project from your github
  2. I assume you have already set up react native on your machine, so skip to "Installing" section and follow those steps.
  3. cd ~/maker-starter-app ; mkdir android/app/src/main/assets (this folder is used during android building)
  4. Build android app. These are the commands I use in the terminal
  5. cd ~/maker-starter-app ; cd android ; ./gradlew clean ; cd ..
  6. react-native bundle --platform android --dev false --entry-file index.js --bundle-output android/app/src/main/assets/index.android.bundle --assets-dest android/app/src/main/res
  7. react-native run-android

Steps 5 and 6 return some warnings, step 7 returns errors like:
e: Incompatible classes were found in dependencies. Remove them from the classpath or use '-Xskip-metadata-version-check' to suppress errors e: /home/my_ubuntu_username/.gradle/caches/transforms-3/2cfe106a332c6a6f2245988cf5920bcb/transformed/jetified-kotlin-stdlib-common-1.6.10.jar!/META-INF/kotlin-stdlib-common.kotlin_module: Module was compiled with an incompatible version of Kotlin. The binary version of its metadata is 1.6.0, expected version is 1.1.15.

The final error says:

FAILURE: Build completed with 2 failures.

1:Task failed with an exception.
What went wrong:
Execution failed for task ':helium_react-native-sdk:compileDebugKotlin'.
Compilation error. See log for more details

Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

2: Task failed with an exception.
What went wrong:
java.lang.StackOverflowError (no error message)

Try:
Run with --stacktrace option to get the stack trace.
Run with --info or --debug option to get more log output.
Run with --scan to get full insights.

Get more help at https://help.gradle.org/

BUILD FAILED in 1m

I found a similar issue on github which seems got fixed, here's the link: segmentio/analytics-react-native#645

Can you please fix this problem on your github project too?
Thanks in advance

universal linking not working on android 12

Hi Sir,

There is a 404 error when the Maker App try to use deep link to Helium App.
78623

We use the Android ADB to catch the log as below:(However, it looks not related to the 404 error)

transform[stderr]: https://github.com/browserslist/browserslist#browsers-data-updating
BUNDLE ./index.js

WARN new NativeEventEmitter() was called with a non-null argument without the required addListener method.
WARN new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.
WARN new NativeEventEmitter() was called with a non-null argument without the required addListener method.
WARN new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.
LOG Running "XXXXXX" with {"rootTag":1}
WARN new NativeEventEmitter() was called with a non-null argument without the required addListener method.
at LanguageProvider (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.XXXXXX.makerapp&modulesOnly=false&runModule=true:313219:24)
at render
at RCTView
at View
at RCTView
at View
at AppContainer (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.XXXXXX.makerapp&modulesOnly=false&runModule=true:76768:36)
at XXXXX(RootComponent) (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.XXXXXX.makerapp&modulesOnly=false&runModule=true:83149:28)
WARN new NativeEventEmitter() was called with a non-null argument without the required removeListeners method.
at LanguageProvider (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.XXXXXX.makerapp&modulesOnly=false&runModule=true:313219:24)
at render
at RCTView
at View
at RCTView
at View
at AppContainer (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.XXXXXX.makerapp&modulesOnly=false&runModule=true:76768:36)
at XXXXXX(RootComponent) (http://localhost:8081/index.bundle?platform=android&dev=true&minify=false&app=com.XXXXXX.makerapp&modulesOnly=false&runModule=true:83149:28)
LOG create ble manager
LOG setting ble log level to verbose
LOG manager create
ERROR Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
in HeliumActionSheet (at MoreListItem.tsx:99)

The App Screenshot:

unnamed (2)

QR code onboarding "Invalid Link" error

Hi Sir,

Question:
When I scan the QR code to do the onboarding, I got "Invalid Link" error.

Please find the procedures. Is there anything wrong?

Step1.

I use the following command in the Miner Hotspot to generate the transaction (the payer is the Maker wallet address)
image (12)

Step 2.

For the QR code I tried two cases.
Case1. use heilum as the scheme name
helium://add_gateway/CrwBCiEBUIUcBTsMCE6Wk1fWy/LN73Mx/q746AESgTy2LZ7+jg8SIQBfUgDQtI/V1bNPim1Hp/xsHUmm+VjkjC+1LSn2YvtVBSJIMEYCIQD/ss9WmpNUSvU/1v8v1MF3OB2Ix2fIvrRFmcvh/wvPfAIhAJWijCZI7pWucVyCbD0CR2h3Yo5YHa2OEESGkA3CvpuZKiEB6PYHrzEv0Y80LE9MajE5Tucv7hofUmBXXXXXXXXXXXXXXXXX=

Result:
It works by using Helium official App=> it shows the owner address, payer address and eth MAC address
It doesn't work by using maker App => it shows "Invalid Link"

Case 2. use maker scheme name
mxxxxx://add_gateway/CrwBCiEBUIUcBTsMCE6Wk1fWy/LN73Mx/q746AESgTy2LZ7+jg8SIQBfUgDQtI/V1bNPim1Hp/xsHUmm+VjkjC+1LSn2YvtVBSJIMEYCIQD/ss9WmpNUSvU/1v8v1MF3OB2Ix2fIvrRFmcvh/wvPfAIhAJWijCZI7pWucVyCbD0CR2h3Yo5YHa2OEESGkA3CvpuZKiEB6PYHrzEv0Y80LE9MajE5Tucv7hofUmBXXXXXXXXXXXXXXXXX=

Result:
It doesn't work by using Helium official App=> it shows mxxx not support
It doesn't work by using maker App => it shows "Invalid Link"

Is there anything I missed and cause this issue?
Please advise. Thanks a lot.

The assist asserting gateway location is unsuccessful during add a new hotspot

Hello, this is our current problem 1. The assist asserting gateway location is unsuccessful during add a new hotspot (you need to set the location again after successful add hotspot, you can set it once for free) 2. The antenna setting during add hotspot is unsuccessful (you need to consume DC to update the antenna after successful add hotspot). Thank you!

Update Assert Location Map

The map for a asserting a location has been updated in the Hotspot app to be more accurate. Should bring these changes over.

Hotspot BEL onboarding problem

Hi Teams,
Last week, it did work to hotspot BLE onboarding when I used my maker-starter-app integrated with my maker setting. But this week, it cannot work using the same maker-starter-app, the onboarding transaction will enter the Pending Transactions section in helium hotspot app, but it disappears after a few minutes. The HNT is not deducted, and the hotspot is not onboarding as well.
Do you have any suggestion for this? Is there any change at Helium backend server?

About api 429 error,and User-Agent set ?

Someone who knows how to set User-Agent in maker-app?
I try helium-hotspot-app-3.10.0-${Platform.OS // }-wallet-client
risinghf-hotspots-app-${getVersion()}-${Platform.OS }-maker-client
risinghf-hotspots-app-${getVersion()}-${Platform.OS }-maker-client ${getUserAgentSync()}
but none of them work. now api all return 429 error 。And can't get any data

api address

https://docs.helium.com/api/blockchain/introduction

Specify a User-Agent
To access the helium api via script you will need to specify a valid User-Agent HTTP header field identifying your agent, all requests made without a User-Agent header will result in an error 429 Slow down gun powder!.

Unable to Onboard a new hotspot using the maker starter app

Hello,

I'm am trying to onboard a new hotspot, but unable to finish the process. I keep getting a 404 hotspot not found when checking the hotspot detail using the helium sdk.
getHotspotDetails(hotspotAddress)

File: HotspotSetupWifiConnectingScreen.tsx
  const goToNextStep = useCallback(async () => {
    const address = await getAddress()
    const hotspot = await getHotspotDetails(hotspotAddress)
    if (hotspot && hotspot.owner === address) {
      navigation.replace('OwnedHotspotErrorScreen')
    } else if (hotspot && hotspot.owner !== address) {
      navigation.replace('NotHotspotOwnerErrorScreen')
    } else {
      navigation.replace('HotspotSetupLocationInfoScreen', {
        hotspotAddress,
        addGatewayTxn,
        hotspotType,
      })
    }
  }, [addGatewayTxn, hotspotAddress, hotspotType, navigation])

It seems like getting the hotspot information is able to be retrieved from the helium api.

How to get keypair for API Authorization

Problem

Our team is developing maker-app base on this repository.
Currently we are migrating update and transfer hotspot features from helium-app,
but encounter an issue 401 authorization fail, when calling API from wallet endpoint https://wallet.api.helium.systems/api

status:401 message: POST url:https://wallet.api.helium.systems/api/transactions]

We need keypair to generate token for the Authorization header in api request,
(keypair are also needed when calling transaction APIs)
but we only could retrieve walletLinkToken when user sign in by linking helium account.

How can we get the keypair for API authorization and transaction signing?
Or is there a way to get keypair from walletLinkToken?


Related Code

src/utils/secureAccount.ts

export const createKeypair = async (
  givenMnemonic: Mnemonic | Array<string> | null = null,
) => {
  ...
  const { keypair: keypairRaw, address } = await Keypair.fromMnemonic(mnemonic)

  await Promise.all([
    setSecureItem('mnemonic', JSON.stringify(mnemonic.words)),
    setSecureItem('keypair', JSON.stringify(keypairRaw)),
    setSecureItem('address', address.b58),
  ])
}

export const getKeypair = async (): Promise<Keypair | undefined> => {
  const keypairStr = await getSecureItem('keypair')
  if (keypairStr) {
    const keypairRaw = JSON.parse(keypairStr)
    return new Keypair(keypairRaw)
  }
}

The different results of scanning QR code between Helium hotspot app and Helium maker-starter-app

Hi Teams,

When we test on QR code on-boarding feature, we encounter the different result of scanning QR code between Helium hotspot app and Helium maker-starter-app.
Helium hotspot app scan our QR code is OK and show confirm information page.
But Helium maker-starter-app scan our QR code is failed and show invalid link.
Our QR code is generated by these instructions (https://docs.helium.com/mine-hnt/full-hotspots/become-a-maker/hotspot-integration-testing/#generate-an-add-hotspot-transaction).
Is there any suggestion? Thanks!

got an error when compile for android

Context

  • react-native-ble-plx: 2.0.3
  • react-native:0.66.3
  • react:17.0.1
  • Platform: Android
  • Android Studio: Arctic Fox 2020.3.1 Patch3

JS logs:

* What went wrong:
Could not determine the dependencies of task ':app:mergeDebugAssets'.
> Could not resolve all task dependencies for configuration ':app:debugRuntimeClasspath'.
   > Could not resolve project :react-native-ble-plx.
     Required by:
         project :app
      > No matching configuration of project :react-native-ble-plx was found. The consumer was configured to find a runtime of a component, as well as attribute 'com.android
.build.api.attributes.BuildTypeAttr' with value 'debug' but:
          - None of the consumable configurations have attributes.

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 2m 54s

is there any solution for this?

ReferenceError: Property 'BigInt' doesn't exist, js engine: hermes

Hi Teams
When I upgraded @helium/react-native-sdk version from 1.0.0 to 2.0.14, I got this error (ReferenceError: Property 'BigInt' doesn't exist, js engine: hermes ). Is there a solution now?

Error: Requiring module "node_modules/@helium/react-native-sdk/src/index.tsx", which threw an exception: ReferenceError: Property 'BigInt' doesn't exist, js engine: hermes

image
image
image

Cannot run in android studio

Shows error

Exception in native call
java.lang.RuntimeException: Unable to load script. Make sure you're either running Metro (run 'npx react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.

and

 couldn't find DSO to load: libjscexecutor.so
  SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/com.maker.makerapp/lib-main flags = 1]
  SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/~~SM_FO6O3ANLmwxQDJoMZ-g==/com.maker.makerapp-W5QRUfWjrBc5oP_vn7fTNw==/lib/arm64 flags = 0]
  SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
  SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
  Native lib dir: /data/app/~~SM_FO6O3ANLmwxQDJoMZ-g==/com.maker.makerapp-W5QRUfWjrBc5oP_vn7fTNw==/lib/arm64
  result: 0

Invalid txn fee when trying to register an hotspot without assert location

"failed_reason": "{invalid,wrong_txn_fee}",

He have my request for this hotspot. so I was successful when sending the location
https://api.helium.io/v1/accounts/14LRiBNfxfdvWNULoXQzPYewHLfZdcZwPJTkDWLbZgZDA1BZpHN/pending_transactions
https://api.helium.io/v1/pending_transactions/qeqkvOjTbsaz3i-RPQN2w42B4jN5qJiS65VGiZeAlIQ

The first object was the response successfully after registering with location.
The last and oldest was without location
Screen_Shot_2022-05-25_at_17 14 21

TypeError: Endpoint URL must start with `http:` or `https:`.

The error message is

2023-05-18 16:33:25.080  8190-8286  ReactNativeJS           com.maker.makerapp                   E  TypeError: Endpoint URL must start with `http:` or `https:`.
                                                                                                
This error is located at:
      in s
      in P
      in n
      in l
      in f
      in RCTView
      in Unknown
      in RCTView
      in Unknown
      in y, js engine: hermes
2023-05-18 16:33:25.084  8190-8286  ReactNativeJS           com.maker.makerapp                   E  TypeError: Endpoint URL must start with `http:` or `https:`.
                                                                                                    
   This error is located at:
      in s
      in P
      in n
      in l
      in f
      in RCTView
      in Unknown
      in RCTView
      in Unknown
      in y, js engine: hermes
2023-05-18 16:33:25.091  8190-8287  unknown:ReactNative     com.maker.makerapp                   E  TypeError: Endpoint URL must start with `http:` or `https:`.
                                                                                                    
   This error is located at:
      in s
      in P
      in n
      in l
      in f
      in RCTView
      in Unknown
      in RCTView
      in Unknown
      in y, js engine: hermes, stack:
   Qe@1710:54527
   e@1710:72702
   anonymous@2196:2632
   useMemo@49:50284
   anonymous@132:6129
   M@2196:2590
   s@2421:2013
   Cr@49:43504
   Sa@49:95925
   vi@49:86899
   gi@49:86801
   hi@49:86566
   oi@49:83486
   pt@49:27332
   Za@49:79770
   Hi@49:95299
   anonymous@49:101549
   anonymous@335:689
   run@332:741
   runApplication@332:1812
   value@34:3797
   anonymous@34:673
   value@34:2503
   value@34:645
2023-05-18 16:33:25.098  8190-8287  unknown:ReactNative     com.maker.makerapp                   E  Exception in native call
                                                                                                    com.facebook.react.common.JavascriptException: TypeError: Endpoint URL must start with `http:` or `https:`.
                                                                                                    
   This error is located at:
      in s
      in P
      in n
      in l
      in f
      in RCTView
      in Unknown
      in RCTView
      in Unknown
      in y, js engine: hermes, stack:
   Qe@1710:54527
   e@1710:72702
   anonymous@2196:2632
   useMemo@49:50284
   anonymous@132:6129
   M@2196:2590
   s@2421:2013
   Cr@49:43504
   Sa@49:95925
   vi@49:86899
   gi@49:86801
   hi@49:86566
   oi@49:83486
   pt@49:27332
   Za@49:79770
   Hi@49:95299
   anonymous@49:101549
   anonymous@335:689
   run@332:741
   runApplication@332:1812
   value@34:3797
   anonymous@34:673
   value@34:2503
   value@34:645
   
      at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(ExceptionsManagerModule.java:72)
      at java.lang.reflect.Method.invoke(Native Method)
      at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
      at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:188)
      at com.facebook.jni.NativeRunnable.run(Native Method)
      at android.os.Handler.handleCallback(Handler.java:938)
      at android.os.Handler.dispatchMessage(Handler.java:99)
      at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
      at android.os.Looper.loop(Looper.java:232)
      at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:228)
      at java.lang.Thread.run(Thread.java:923)

visual bugg

image

Hello,I have found another visual bugg. If I'm using the cotx app to update antenna dbi and input a value like 1.2dbi the confirmation prompt I get sent to says 12 and not 1.2

stuck at network setting when adding hotspot via maker app

Hi Teams,
I am trying to build and use the maker app, when I try to add the hotspot feature, I can scan the hotspot and connect via BLE, but go to the network setting step, I can't scan wifi instead or choose to use ethernet or any whatever else it seems to be stuck here, while I can still add hotspot using helium app.
Do you have any suggestions for this?. Does the maker app fully support adding the hotspot feature?

Thanks!
image
image

TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[34], "@helium/react-native-sdk").SolanaProvider')

When I integrate the code, when running on the real machine (both android and ios), an error is reported:
"node_modules/@helium/react-native-sdk/src/index.tsx", which threw an exception: ReferenceError: Can't find variable: BigInt', '\nApp@/var/containers/Bundle/Application/54E2D123-2E77-4B5C-9339-99515B70EC0E/XXX.app/main
] TypeError: undefined is not an object (evaluating '_$$_REQUIRE(_dependencyMap[34], "@helium/react-native-sdk").SolanaProvider')

image

Here are the versions of the libraries I depend on in my package.json
"react": "17.0.2",
"@helium/react-native-sdk": "^2.0.10",
"react-native": "0.66.3",

Is there a solution?

HotspotSetupBluetoothSuccess report invalid checksum

when i donwload the newest make app and run it on my phone and onboarding my gateway, it report 'invalid checksum' when the app code run at

+++ b/src/features/hotspots/setup/HotspotSetupBluetoothSuccess.tsx
@@ -126,10 +126,16 @@ const HotspotSetupBluetoothSuccess = () => {
if (!parsed?.address) throw new Error('Invalid Token')

       const { address: ownerAddress } = parsed
  • try {
    const addGatewayTxn = await createGatewayTxn({
    ownerAddress,
    payerAddress,
    })
  • } catch (e) {
  •   alert('aaaa add gateway txn... owner ' + ownerAddress)
    
  •   alert('aaaa add gateway txn... payer ' + payerAddress)
    
  • }
    navigation.replace('HotspotSetupPickWifiScreen', {

Invalid link from transferring hotspot

Hi Teams,

We test this new feature (transfer hotspot) and encounter the following problem:
When we key in our hotspot address and new owner address and it will redirect to helium hotspot app and show the invalid link page.
Do you have any suggestion for this?

S__16293924

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.