profile
viewpoint
bulletproofapps™ mjstelly bulletproofapps™ Fayetteville, AR Customers demand solid, feature-rich mobile apps. Make their apps bulletproof.

mjstelly/food 0

tutorial source for Udemy react native course

mjstelly/HiltonRes 0

Demo app highlighting graphql and apollo-client

mjstelly/sandbox 0

Playground for testing react native features

mjstelly/vsc_test 0

VSCode bug test for Javascript Update Imports On File Move

mjstelly/watermelondb_demo 0

Initial foundation for updated React Native WatermelonDB demo

issue commentmicrosoft/vscode-react-native

[Bug][Expo] XDLError: packagerPort must be an integer

That's interesting because the expo-cli team punted me to this repo saying it wasn't their issue. At any rate, thanks for updating me.

mjstelly

comment created time in a month

issue openedmicrosoft/vscode-react-native

[Bug][Expo] XDLError: packagerPort must be an integer

🐛 What is the bug? How can we reproduce it?

This is my third stop in the dependency chain regarding this issue: expo-cli, vscode, and now, here. I hope this issue can be resolved here.

  1. In VSC, create a debug config for Expo
        {
            "name": "Debug in Exponent",
            "cwd": "${workspaceFolder}",
            "type": "reactnative",
            "request": "launch",
            "platform": "exponent"
        }
  1. Launch the config in the debugger

Expected behavior

The IDE launches my app in debug mode.

Debug output

<details> <summary>Debug Console</summary>


OS: darwin x64
Adapter node: v12.8.1 x64
vscode-chrome-debug-core: 6.8.8
Could not debug. packagerPort must be an integer

</details>

<details> <summary>React Native output channel</summary>


[Info] Making sure your project uses the correct dependencies for Expo. This may take a while...

Checking if this is Expo app......
[Info] Starting Packager

┌──────────────────────────────────────────────────────────────────────────────┐
│                                                                              │
│  Running Metro Bundler on port 8081.                                         │
│                                                                              │
│  Keep Metro running while developing on any JS projects. Feel free to        │
│  close this tab and run your own Metro instance if you prefer.               │
│                                                                              │
│  https://github.com/facebook/react-native                                    │
│                                                                              │
└──────────────────────────────────────────────────────────────────────────────┘

Looking for JS files in
   /Users/me/Documents/projects/my-project

Loading dependency graph, done.
[Info] Packager started.

[Info] Prewarming bundle cache. This may take a while ...

[Info] Building and running application.

[Error] XDLError: packagerPort must be an integer

</details>

<details> <summary>Developer Tools console</summary>


console.ts:137 [Extension Host] (node:63102) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ console.ts:137
console.ts:137 [Extension Host] (node:63102) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
t.log @ console.ts:137
console.ts:137 [Extension Host] No editors associated with document: /Users/me/Documents/projects/my-project/.vscode/launch.json
t.log @ console.ts:137
console.ts:137 [Extension Host] (node:63102) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ console.ts:137
console.ts:137 [Extension Host] (node:63102) [DEP0022] DeprecationWarning: os.tmpDir() is deprecated. Use os.tmpdir() instead.
t.log @ console.ts:137
log.ts:197   ERR No application in the Launch Services database matches the input criteria.: Error: No application in the Launch Services database matches the input criteria.

</details>

Environment

Please tell us about your system and your project:

npx expo doctor
┌─────────────────────────────────────────────────────────────────────────┐
│                                                                         │
│   There is a new version of expo-cli available (3.21.13).               │
│   You are currently using expo-cli 3.21.10                              │
│   Install expo-cli globally using the package manager of your choice;   │
│   for example: `npm install -g expo-cli` to get the latest version      │
│                                                                         │
└─────────────────────────────────────────────────────────────────────────┘
Didn't find any issues with your project!
  • envinfo:
System:
    OS: macOS 10.15.5
    CPU: (4) x64 Intel(R) Core(TM) m3-6Y30 CPU @ 0.90GHz
    Memory: 29.67 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.18.1 - ~/.nvm/versions/node/v12.18.1/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.5 - ~/.nvm/versions/node/v12.18.1/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
    Homebrew: 2.4.0 - /usr/local/bin/brew
    pip3: 20.0.2 - /usr/local/bin/pip3
    RubyGems: 3.0.3 - /usr/bin/gem
  Utilities:
    Make: 3.81 - /usr/bin/make
    GCC: 4.2.1 - /usr/bin/gcc
    Git: 2.21.1 - /usr/bin/git
    Clang: 1100.0.33.17 - /usr/bin/clang
    Subversion: 1.10.4 - /usr/bin/svn
  Servers:
    Apache: 2.4.41 - /usr/sbin/apachectl
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
  IDEs:
    Android Studio: 3.6 AI-192.7142.36.36.6241897
    Nano: 2.0.6 - /usr/bin/nano
    VSCode: 1.46.1 - /usr/local/bin/code
    Vim: 8.1 - /usr/bin/vim
    Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
  Languages:
    Bash: 3.2.57 - /bin/bash
    Java: 1.8.0_242 - /usr/bin/javac
    Perl: 5.18.4 - /usr/bin/perl
    PHP: 7.3.11 - /usr/bin/php
    Python: 2.7.16 - /usr/bin/python
    Python3: 3.7.7 - /usr/local/bin/python3
    Ruby: 2.6.3 - /usr/bin/ruby
  Databases:
    SQLite: 3.28.0 - /usr/bin/sqlite3
  Browsers:
    Brave Browser: 83.1.10.95
    Chrome: 83.0.4103.116
    Safari: 13.1.1
  • React Native Tools extension version: 0.16.0
  • Expo SDK version (if applicable): 38.0.4

created time in 2 months

issue commentexpo/expo-cli

XDLError: packagerPort must be an integer

I opened an issue with VSCode. They, too, punted on the issue.

mjstelly

comment created time in 2 months

issue openedmicrosoft/vscode

VSC debugger error: XDLError: packagerPort must be an integer

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ --> <!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ --> <!-- Please search existing issues to avoid creating duplicates. --> <!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->

  • VSCode Version: 1.46.1
  • OS Version: macOS 10.15.5
  • Platform: React Native 0.61.x, Expo: 37.0.3

The expo-cli authors requested I open an issue here. They believe it's a problem with how the VSC debugger connects to Expo. Please reference this issue, XDLError: packagerPort must be an integer for details.

<!-- Launch with code --disable-extensions to check. --> Does this issue occur when all extensions are disabled?: Yes (sort of). The expo debugger won't run at all if extensions are disabled because it depends on the React Native Tools extension. Of course, the reactnative issue goes away when extensions are re-enabled. That leaves me with 3 dependencies: VSC, React Native Tools, Expo. I hope someone can help. Javascript debugging is enough of a chore already without having to wrestle with the tools.

Please advise.

Screen Shot 2020-06-28 at 10 12 24 AM

        {
            "name": "Debug in Exponent",
            "cwd": "${workspaceFolder}",
            "type": "reactnative",
            "request": "launch",
            "platform": "exponent"
        }

created time in 2 months

issue commentexpo/expo-cli

XDLError: packagerPort must be an integer

The VSC issue template recommends loading the IDE w/o extensions using code --disable-extensions. I did so. The debugger failed to launch. This leaves me with a third dependency, React Native Tools that mucks up the works. At this point, I don't have the time to run down this rabbit hole. I hope someone finds this and can offer a solution. Screen Shot 2020-06-28 at 10 04 51 AM

mjstelly

comment created time in 2 months

issue closedexpo/expo-cli

XDLError: packagerPort must be an integer

Description

Today is the first time I've used Expo for any production code. I've encountered this error:

[Error] XDLError: packagerPort must be an integer

the first time I've tried to use the VSC Expo debug configuration. This error does not occur when launching expo normally.

Expected Behavior

Use case: Debug expo app using VSC integrated debugger.

  1. Add expo config to launch.json
  2. In Debug mode, run the configuration

Expected app to launch in debug mode

Observed Behavior

Upon launching the debug config, the bundler starts successfully. However, immediately after that, I receive the following console output terminating the launch process. It is unrecoverable and the app will not launch in debug mode at all.

Loading dependency graph, done.
[Info] Packager started.

[Info] Prewarming bundle cache. This may take a while ...

[Info] Building and running application.

[Error] XDLError: packagerPort must be an integer

Environment

Debug config:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug in Exponent",
      "cwd": "${workspaceFolder}",
      "type": "reactnative",
      "request": "launch",
      "platform": "exponent"
    }
  ]
}

Diagnostics

Expo CLI 3.21.9 environment info:
    System:
      OS: macOS 10.15.5
      Shell: 5.7.1 - /bin/zsh
    Binaries:
      Node: 12.18.1 - ~/.nvm/versions/node/v12.18.1/bin/node
      Yarn: 1.22.4 - /usr/local/bin/yarn
      npm: 6.14.5 - ~/.nvm/versions/node/v12.18.1/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.6 AI-192.7142.36.36.6241897
      Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~37.0.3 => 37.0.10 
      react: ~16.9.0 => 16.9.0 
      react-dom: ~16.9.0 => 16.9.0 
      react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4 
      react-native-web: ~0.11.7 => 0.11.7 
      react-navigation: ^4.3.9 => 4.3.9 

<!--

Please run expo diagnostics in the project folder and copy the output here:

Also specify:

  • Phone/emulator/simulator platform, model and version:

-->

Reproducible Demo

I do not have a demo. <!-- Please provide a minimized reproducible demonstration of the problem you're reporting.

Issues that come with minimal repro's are resolved much more quickly than issues where a maintainer has to reproduce themselves. -->

closed time in 2 months

mjstelly

issue commentexpo/expo-cli

XDLError: packagerPort must be an integer

I appreciate the response. It may be an issue with VSC's handling of the expo debugger. I can use their debugger with no problem on my non-expo apps. I'll see what they have to say about it.

mjstelly

comment created time in 2 months

issue openedexpo/expo-cli

XDLError: packagerPort must be an integer

Description

Today is the first time I've used Expo for any production code. I've encountered this error:

[Error] XDLError: packagerPort must be an integer

the first time I've tried to use the VSC Expo debug configuration. This error does not occur when launching expo normally.

Expected Behavior

Use case: Debug expo app using VSC integrated debugger.

  1. Add expo config to launch.json
  2. In Debug mode, run the configuration

Expected app to launch in debug mode

Observed Behavior

Upon launching the debug config, the bundler starts successfully. However, immediately after that, I receive the following console output terminating the launch process. It is unrecoverable and the app will not launch in debug mode at all.

Loading dependency graph, done.
[Info] Packager started.

[Info] Prewarming bundle cache. This may take a while ...

[Info] Building and running application.

[Error] XDLError: packagerPort must be an integer

Environment

Debug config:

{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug in Exponent",
      "cwd": "${workspaceFolder}",
      "type": "reactnative",
      "request": "launch",
      "platform": "exponent"
    }
  ]
}

Diagnostics

Expo CLI 3.21.9 environment info:
    System:
      OS: macOS 10.15.5
      Shell: 5.7.1 - /bin/zsh
    Binaries:
      Node: 12.18.1 - ~/.nvm/versions/node/v12.18.1/bin/node
      Yarn: 1.22.4 - /usr/local/bin/yarn
      npm: 6.14.5 - ~/.nvm/versions/node/v12.18.1/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    IDEs:
      Android Studio: 3.6 AI-192.7142.36.36.6241897
      Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
    npmPackages:
      expo: ~37.0.3 => 37.0.10 
      react: ~16.9.0 => 16.9.0 
      react-dom: ~16.9.0 => 16.9.0 
      react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4 
      react-native-web: ~0.11.7 => 0.11.7 
      react-navigation: ^4.3.9 => 4.3.9 

<!--

Please run expo diagnostics in the project folder and copy the output here:

Also specify:

  • Phone/emulator/simulator platform, model and version:

-->

Reproducible Demo

I do not have a demo. <!-- Please provide a minimized reproducible demonstration of the problem you're reporting.

Issues that come with minimal repro's are resolved much more quickly than issues where a maintainer has to reproduce themselves. -->

created time in 2 months

issue commentandpor/react-native-sqlite-storage

[Question] Are you even supporting this package anymore?

Touchè. Point taken. I'll stick to raising substantive issues rather than philosophical ones.

mjstelly

comment created time in 2 months

issue commentandpor/react-native-sqlite-storage

[ios] app doesn't find pre-populated database

should it not be just a function pointer?

You are correct. I obviously needed sleep. After looking at the same code for 8 hours, I got lost in the weeds.

Once that database is created, module will no longer use your input database as template until you delete that database.

Ok. I get that once created there's no need to recreate. However, I'm missing is the API doc. Am I simply not finding it? The README says how to create and open the database, but I need to know how to check for exists(), isOpen() or !isClosed(), etc. Where are the methods, properties, and functions documented? That would go a long way in helping me resolve my own issues.

mjstelly

comment created time in 2 months

issue commentandpor/react-native-sqlite-storage

[Question] Are you even supporting this package anymore?

On top of it, there are 4 demo files showing all aspects of library functionality. They all work, have been tested and most folks have no problems.

I agree with a great many of your assertions. A lot of the issues I'm experiencing stem from my lack of understanding of the module's API. With that said, I think the responsibility lay with the author to rectify areas of misunderstanding. Of course, the reporter has to meet you halfway. Far too many folks think we're mind readers here to magically solve their coding issues.

But hey, we're all learning here. I appreciate your efforts. I will do what I can to meet you in the middle to resolve any issues I have.

mjstelly

comment created time in 2 months

issue openedandpor/react-native-sqlite-storage

[ios] app doesn't find pre-populated database

<!--- Provide a general summary of the issue in the Title above --> Based on the output here, can someone advise me what I am doing wrong?

I followed the steps in the doc to use a pre-populated database for ios. I have no idea why the app is creating and using an identically-named database file.

Assuming all other setup is correct, the file path is <root>/www/appData.sqlite Screen Shot 2020-06-15 at 2 18 27 PM

I have my config

const dbConfig = {
  name: 'appData.sqlite',
  createFromLocation: 1, //ios only
};

I have 2 callbacks

  onSuccess = () => {
    console.log('========= DB opened successfully ========');
  };

  onError = () => {
    console.log('========= Error opening db ========');
  };

I have two rows of data

partner_id,partner_name,icon,color,text_color
1,ferguson,AppImages.badgeFerguson,colors.ferguson,colors.white05
2,ecobee,AppImages.badgeFerguson,colors.ecobee,colors.white05

I have a function to fetch the data

  async getPartners() {
    const partners = await this.database.executeSql(queries.fetchPartners);

    return partners[0].rows.raw();
  }
}

using the following query SELECT * FROM partners;

And I have the actual call this.database = await SQLite.openDatabase(dbConfig, this.onSuccess(), this.onError());

Expected Behavior

Given this setup, I would expect that

  1. either the onsuccess or onerror message would display
  2. two pre-existing rows would output.

Current Behavior

What actually happens Both the success and error messages display

Promise based runtime ready
========= DB opened successfully ========
========= Error opening db ========

Some unknown appData.sqlite file is opened

OPEN database: appData.sqlite
SQLite.open({"name":"appData.sqlite","createFromLocation":1,"dblocation":"nosync","assetFilename":"1"})
new transaction is waiting for open operation
Built path to pre-populated DB asset from app bundle www subdirectory: /Users/michaelstelly/Library/Developer/CoreSimulator/Devices/23EA4039-E854-4FF6-B296-03E1BA488F1A/data/Containers/Bundle/Application/368707F9-DD7F-40EB-A6A0-6326D2BF12DF/HomeeProvider.app/www/appData.sqlite
target database location: nosync
Opening db in mode READ_WRITE, full path: /Users/michaelstelly/Library/Developer/CoreSimulator/Devices/23EA4039-E854-4FF6-B296-03E1BA488F1A/data/Containers/Data/Application/3178FFD8-7A73-4030-AA63-B07CDEB4E633/Library/LocalDatabase/appData.sqlite
Database opened
Good news: SQLite is thread safe!
DB opened: appData.sqlite

And when I output the partners table to a console table, I get 2 rows added from inside that app.

┌─────────┬──────┬───────┐
│ (index) │  id  │ name  │
├─────────┼──────┼───────┤
│    0    │ null │ 'PED' │
│    1    │ null │ 'PED' │
└─────────┴──────┴───────┘

Your Environment

<!--- Include as many relevant details about the environment you experienced the bug in -->

  • React Native SQLite Storage Version used: "react-native-sqlite-storage": "^5.0.0",
  • React Native version used:
    "react": "16.11.0",
    "react-native": "0.62.2",
  • Operating System and version (simulator or device): ios 13.4.1
  • IDE used: Visual Studio Code

created time in 2 months

issue closedandpor/react-native-sqlite-storage

[Question] Are you even supporting this package anymore?

It looks like this project has been abandoned. Is that so? No updates in the past year, unresolved issues were closed.

Any thoughts on whether or not we can expect any support or updates any time soon?

closed time in 2 months

mjstelly

issue commentandpor/react-native-sqlite-storage

[Question] Are you even supporting this package anymore?

Issues #48 and #288 are specific examples. The first being the most relevant. Fortunately, a colleague of mine was able to resolve the issue in his branch. I didn't have time to analyze what he did differently. I just picked up where he left off. I understand that this is an OSS project and my question was unnecessarily aggressive. I apologize. I let my frustration and need for a working solution cloud my judgment.

If there is something on which I can help, I will. It's better to be part of the solution than part of the problem. Thanks for your response.

mjstelly

comment created time in 2 months

fork mjstelly/react-native-sqlite-storage

Full featured SQLite3 Native Plugin for React Native (Android and iOS)

fork in 2 months

issue openedandpor/react-native-sqlite-storage

[Question] Are you even supporting this package anymore?

It looks like this project has been abandoned. Is that so? No updates in the past year, unresolved issues were closed.

Any thoughts on whether or not we can expect any support or updates any time soon?

created time in 2 months

issue commentNozbe/WatermelonDB

Manually adding Xcode library crashes build

At my next opportunity, I’ll get you more detail. For now, watermelon is not stable enough nor has the proper JSI for us to proceed with implementation.

You have a good start, but are in dire need of a retooling for ESnext and ReactNative > 0.60. Good luck.

mjstelly

comment created time in 2 months

issue openedNozbe/WatermelonDB

Manually adding Xcode library crashes build

I don't know how I got my demo app working before, but it must've been pure luck. I revisited the app today. No changes had been made to the code since last Friday. While attempting to build it for iOS, the compiler crashed with a log file full of Swift errors. I have no idea why.

Here are the steps to recreate my issue.

If I remove libWatermelonDB.a from the project, the app will build in Xcode. If I remove/re-add the .xcodeproj file and the library. BOOM! Crashes again. It's definitely not my app causing problems. It's the WatermelonDB project.

I've tried multiple times linking/unlinking the library both through Xcode and using react-native link/unlink. I get the same result every time.

I've attached the project. Just unzip it, install node modules and pod files as usual. I hope someone can decipher what the hell the problem is. Thanks.

homee_wdb-feature-demo.zip

created time in 2 months

created repositorymjstelly/watermelondb_demo

Initial foundation for updated React Native WatermelonDB demo

created time in 2 months

issue commentNozbe/WatermelonDB

React-native example app not working

I have an RN project already started. I’ll post it to my public github. You can fork it if you wish. @radex @sofiageo

sofiageo

comment created time in 2 months

issue closedNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I followed the instructions for creating the db tutorial. I got the following error Unhandled JS Exception: TypeError: Cannot read property 'initialize' of undefined. Thinking I did something wrong, I recreated it. Same error. I've scoured the internet for a solution without success.

My environment package.json

{
  "name": "movie_directory",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "@nozbe/watermelondb": "^0.16.1",
    "@nozbe/with-observables": "^1.0.5",
    "native-base": "^2.13.12",
    "rambdax": "^3.7.0",
    "react": "16.11.0",
    "react-native": "0.62.2",
    "react-native-fullwidth-image": "^0.1.3",
    "react-native-gesture-handler": "^1.6.1",
    "react-navigation": "^4.3.9"
  },
  "devDependencies": {
    "@babel/core": "^7.6.2",
    "@babel/plugin-proposal-decorators": "^7.8.3",
    "@babel/runtime": "^7.6.2",
    "@react-native-community/eslint-config": "^0.0.5",
    "babel-jest": "^24.9.0",
    "eslint": "^6.5.1",
    "jest": "^24.9.0",
    "metro-react-native-babel-preset": "^0.58.0",
    "react-test-renderer": "16.11.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

The error occurs in the index.js file when it can't initialize the SQLiteAdapter. Is there any known issues with using Watermelon with the latest react-native version? This is a blocker because the app does not compile.

Here is the index.js file // index.js

import {AppRegistry} from 'react-native';
import App from './App';
import {name as appName} from './app.json';

import {Database} from '@nozbe/watermelondb';
import SQLiteAdapter from '@nozbe/watermelondb/adapters/sqlite';
import {mySchema} from './src/models/schema';
import {dbModels} from './src/models/index.js';

// First, create the adapter to the underlying database:
const adapter = new SQLiteAdapter({
  dbName: 'WatermelonDemo',
  schema: mySchema,
});

// Then, make a Watermelon database from it!
const database = new Database({
  adapter,
  modelClasses: dbModels,
});

AppRegistry.registerComponent(appName, () => App);

closed time in 2 months

mjstelly

issue commentNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I've continued to poke around. I found that I missed a step when manually linking the Xcode lib file. I linked the libWatermelonDB.a and reran the app. It appears to have fixed the original issue. It uncovered a different issue that was blocked by this. This was a painful lesson that I hope someone else can learn from. Now it's to progress to the next bug.

mjstelly

comment created time in 2 months

issue commentmicrosoft/vscode

Auto-update Javascript paths fails

The test project can be found here. To test:

  1. Open the project in VSC
  2. Check that the setting Update Imports On File Move: Enabled is set to always
  3. With no files open in the editor, drag App.js to the /src folder.
  4. Open index.js.

Result: Expected import: import App from './src/App'; Actual import: import App from './App';

If index.js is open in the editor and the file is moved, VSC will update the path. Also, if the import path is incorrect and the file is relocated to its original spot, the import will not update.

mjstelly

comment created time in 2 months

create barnchmjstelly/vsc_test

branch : master

created branch time in 2 months

created repositorymjstelly/vsc_test

VSCode bug test for Javascript Update Imports On File Move

created time in 2 months

issue commentNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I thought that maybe the problem was in not manually linking the node module. I tried linking it through Xcode. Same error. I manually unlinked and re-linked through CLI and reran. Doing that caused wall of error text.

Finally, I manually unlinked and let RN auto-link it with pod install. I received the same message [!] use_native_modules! skipped the react-native dependency '@nozbe/watermelondb'. No podspec file was found. Launching the app returns me back to the original undefined error.

mjstelly

comment created time in 2 months

IssuesEvent

issue commentNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I'm reopening because the issue still exists when working from a fresh install. Thanks, @jdnichollsc for assistance. But your app is written in Typescript which I don't use. I followed the tutorial verbatim except for passing the database object to the navigation handler. I don't need it for this PoC. Also, I factored db ops into it's own component.

Database.js

import {Database} from '@nozbe/watermelondb';
import SQLiteAdapter from '@nozbe/watermelondb/adapters/sqlite';

import {mySchema} from '../models/schema';
import {Post, Comment} from '../models/Post';

// First, create the adapter to the underlying database:
const adapter = new SQLiteAdapter({
  mySchema,
});

// Then, make a Watermelon database from it!
const HomeeDb = new Database({
  adapter,
  modelClasses: [Post, Comment],
  actionsEnabled: true,
});

export default HomeeDb;

I import this into App.js with import {HomeeDb} from './services/Database'; Then call it with const db = HomeeDb();. The app crashes when trying to initialize the adapter. I tried to step through it but it's crashing in the node module.

mjstelly

comment created time in 2 months

issue closedNozbe/WatermelonDB

[Website issue] Link to doc is broken

The url for the link to your documentation is self-referencing. It should probably point to the installation doc..

closed time in 2 months

mjstelly

issue commentNozbe/WatermelonDB

[Website issue] Link to doc is broken

I was wrong. The link points to a web-rendered version of the markdown files. The header text is so faint I totally missed it. May want to change the font color.

mjstelly

comment created time in 2 months

issue openedNozbe/WatermelonDB

[Website issue] Link to doc is broken

The url for the link to your documentation is self-referencing. It should probably point to the installation doc..

created time in 2 months

created repositorymjstelly/watermelon_db_demo

created time in 2 months

issue openedNozbe/WatermelonDB

Support for react-native auto-link

As of Sept 2019, there was no support for the RN auto-linking for 0.60+. Has that functionality been added to your roadmap?

My current packages

    "@nozbe/watermelondb": "^0.16.1",
    "@nozbe/with-observables": "^1.0.5",
    "react": "16.11.0",
    "react-native": "0.62.2",

As of this RN version, I still get [!] use_native_modules! skipped the react-native dependency '@nozbe/watermelondb'. No podspec file was found. The test app compiles, but I haven't implemented wdb in the app yet. So I don't know if this is a latent bug or not.

created time in 2 months

issue openedmicrosoft/vscode

Auto-update Javascript paths fails

Issue Type: <b>Bug</b>

Use case: Given: I want to move a .js file to another folder, When: I relocate the file, I want VSC to update the import path reference, Then: the app will compile successfully

Current settings "javascript.updateImportsOnFileMove.enabled": "prompt"

Example: Move ./App.js to ./src/App.js

Result: Expected: VSC prompts me to update the import path Actual: No prompt and no update occur.

VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:33:47.663Z) OS version: Darwin x64 19.4.0

<details> <summary>System Info</summary>

Item Value
CPUs Intel(R) Core(TM) i7-7660U CPU @ 2.50GHz (4 x 2500)
GPU Status 2d_canvas: enabled<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>protected_video_decode: unavailable_off<br>rasterization: enabled<br>skia_renderer: disabled_off_ok<br>video_decode: enabled<br>viz_display_compositor: enabled_on<br>viz_hit_test_surface_layer: disabled_off_ok<br>webgl: enabled<br>webgl2: enabled
Load (avg) 2, 2, 3
Memory (System) 16.00GB (1.69GB free)
Process Argv
Screen Reader no
VM 0%

</details><details><summary>Extensions (19)</summary>

Extension Author (truncated) Version
project-manager ale 11.0.1
vscode-apollo apo 1.16.0
npm-intellisense chr 1.3.0
path-intellisense chr 1.4.2
bracket-pair-colorizer Coe 1.0.61
vscode-eslint dba 2.1.5
gitlens eam 10.2.1
vscode-npm-script eg2 0.3.12
vsc-material-theme Equ 32.6.0
vsc-material-theme-icons equ 1.1.4
prettier-vscode esb 4.7.0
gitignore mic 1.0.1
atom-keybindings ms- 3.0.8
vsliveshare ms- 1.0.2236
debugger-for-chrome msj 4.12.8
vscode-react-native msj 0.16.0
code-settings-sync Sha 3.4.3
autoimport ste 1.5.3
alphabetical-sorter ue 2.0.1

(3 theme extensions excluded)

</details> <!-- generated by issue reporter -->

created time in 2 months

issue commentproyecto26/MyApp

TypeError: Cannot read property 'closed' of null

Oops. In my haste I forgot to complete the description.

mjstelly

comment created time in 2 months

issue openedproyecto26/MyApp

TypeError: Cannot read property 'closed' of null

App crashes when navigating from Offline list back to Photo list.

Steps to reproduce: Launch app and press start button Open drawer menu Select Offline list Reopen drawer menu Select Photo list app crash

created time in 2 months

issue closedNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I followed the instructions for creating the db tutorial. I got the following error Unhandled JS Exception: TypeError: Cannot read property 'initialize' of undefined. Thinking I did something wrong, I recreated it. Same error. I've scoured the internet for a solution without success.

My environment package.json

{
  "name": "movie_directory",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "@nozbe/watermelondb": "^0.16.1",
    "@nozbe/with-observables": "^1.0.5",
    "native-base": "^2.13.12",
    "rambdax": "^3.7.0",
    "react": "16.11.0",
    "react-native": "0.62.2",
    "react-native-fullwidth-image": "^0.1.3",
    "react-native-gesture-handler": "^1.6.1",
    "react-navigation": "^4.3.9"
  },
  "devDependencies": {
    "@babel/core": "^7.6.2",
    "@babel/plugin-proposal-decorators": "^7.8.3",
    "@babel/runtime": "^7.6.2",
    "@react-native-community/eslint-config": "^0.0.5",
    "babel-jest": "^24.9.0",
    "eslint": "^6.5.1",
    "jest": "^24.9.0",
    "metro-react-native-babel-preset": "^0.58.0",
    "react-test-renderer": "16.11.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

The error occurs in the index.js file when it can't initialize the SQLiteAdapter. Is there any known issues with using Watermelon with the latest react-native version? This is a blocker because the app does not compile.

Here is the index.js file // index.js

import {AppRegistry} from 'react-native';
import App from './App';
import {name as appName} from './app.json';

import {Database} from '@nozbe/watermelondb';
import SQLiteAdapter from '@nozbe/watermelondb/adapters/sqlite';
import {mySchema} from './src/models/schema';
import {dbModels} from './src/models/index.js';

// First, create the adapter to the underlying database:
const adapter = new SQLiteAdapter({
  dbName: 'WatermelonDemo',
  schema: mySchema,
});

// Then, make a Watermelon database from it!
const database = new Database({
  adapter,
  modelClasses: dbModels,
});

AppRegistry.registerComponent(appName, () => App);

closed time in 2 months

mjstelly

issue commentNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

Thanks, @jdnichollsc, your demo may come in handy.

mjstelly

comment created time in 2 months

issue commentNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I’m attempting to create a working demo based on a tutorial using the code I posted. I’ve been unsuccessful. The app crashes before it can load App.js.

mjstelly

comment created time in 3 months

issue closedfacebook/flipper

Question: VSC + flipper: Why do we need dev repo

First off: I like that Flipper can be integrated into VSC debugger at all. That's a good start to making the tool a one-stop deb shop. However, I have a question. Why do the instructions for adding Flipper to VSC involve using the dev repo vs. the production app? VSC Debugging

closed time in 3 months

mjstelly

issue openedfacebook/flipper

Question: VSC + flipper: Why do we need dev repo

First off: I like that Flipper can be integrated into VSC debugger at all. That's a good start to making the tool a one-stop deb shop. However, I have a question. Why do the instructions for adding Flipper to VSC involve using the dev repo vs. the production app? VSC Debugging

created time in 3 months

issue openedNozbe/WatermelonDB

[Tutorial] Cannot read property 'initialize' of undefined

I followed the instructions for creating the db tutorial. I got the following error Unhandled JS Exception: TypeError: Cannot read property 'initialize' of undefined. Thinking I did something wrong, I recreated it. Same error. I've scoured the internet for a solution without success.

My environment package.json

{
  "name": "movie_directory",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "android": "react-native run-android",
    "ios": "react-native run-ios",
    "start": "react-native start",
    "test": "jest",
    "lint": "eslint ."
  },
  "dependencies": {
    "@nozbe/watermelondb": "^0.16.1",
    "@nozbe/with-observables": "^1.0.5",
    "native-base": "^2.13.12",
    "rambdax": "^3.7.0",
    "react": "16.11.0",
    "react-native": "0.62.2",
    "react-native-fullwidth-image": "^0.1.3",
    "react-native-gesture-handler": "^1.6.1",
    "react-navigation": "^4.3.9"
  },
  "devDependencies": {
    "@babel/core": "^7.6.2",
    "@babel/plugin-proposal-decorators": "^7.8.3",
    "@babel/runtime": "^7.6.2",
    "@react-native-community/eslint-config": "^0.0.5",
    "babel-jest": "^24.9.0",
    "eslint": "^6.5.1",
    "jest": "^24.9.0",
    "metro-react-native-babel-preset": "^0.58.0",
    "react-test-renderer": "16.11.0"
  },
  "jest": {
    "preset": "react-native"
  }
}

The error occurs in the index.js file when it can't initialize the SQLiteAdapter. Is there any known issues with using Watermelon with the latest react-native version? This is a blocker because the app does not compile.

created time in 3 months

issue commentnvie/gitflow

git flow init fails on cloned repo.

The fact that this issue has remained open for 9 years says a lot about our chances that it'll get resolved any time soon.

OJ

comment created time in 3 months

issue commentnvie/gitflow

git flow init fails on cloned repo.

@andres310597 That may be the answer for you. It did not help on my repo.

➜  mobile_provider git:(develop) git checkout master   
Updating files: 100% (17199/17199), done.
Switched to branch 'master'
Your branch is up to date with 'origin/master'. 
➜  mobile_provider git:(master) ✗ git checkout develop
Updating files: 100% (17199/17199), done.
Switched to branch 'develop'
Your branch is up to date with 'origin/develop'.                                                            /3.1s
➜  mobile_provider git:(develop) git flow init       

Which branch should be used for integration of the "next release"?
   - bug/mstelly/prov/2449-leave-job-crash
   - master
   - poc/realmdb
Branch name for "next release" development: [develop]
OJ

comment created time in 3 months

fork mjstelly/MovieDirectory

A React Native application using WatermelonDB to create offline first applications.

fork in 3 months

issue commentNozbe/WatermelonDB

React-native example app not working

The example RN is way out of date. @sofiageo said he's working on updating it, but that was a while ago. If I had the time, I would. I'm too busy researching offline storage solutions.

sofiageo

comment created time in 3 months

more