Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Basic Example Displays "Unable to Load" every 1/4 times it's displayed #27

Open
kyle-ssg opened this issue Jul 30, 2018 · 4 comments
Open

Comments

@kyle-ssg
Copy link

kyle-ssg commented Jul 30, 2018

Description

Swiping between widgets and the desktop I find that every 1/4 times the widget displays "Unable to load"

Steps to reproduce

Wait on home screen 3-4 seconds and swipe to widget screen, repeat several times

System configuration

Please add result of react-native info command and react-native-today-widget version used


react-native-today-widget 1.0.0

Environment:
  OS: macOS High Sierra 10.13.4
  Node: 9.8.0
  Yarn: 1.3.2
  npm: 5.6.0
  Watchman: 4.9.0
  Xcode: Xcode 9.4.1 Build version 9F2000
  Android Studio: 2.3 AI-162.4069837

Packages: (wanted => installed)
  react: 16.3.1 => 16.3.1
  react-native: 0.55.4 => 0.55.4

This is a real shame at the moment as when this does work it's awesome, seriously great work making this library!

Edit: I can only replicate this on an actual device, it always works on the simulator.

@kyle-ssg
Copy link
Author

kyle-ssg commented Jul 30, 2018

I think this is due to even the basic app using too much memory, I found this was fixed by doing a few things, I upgraded react native and removed any dev dependencies:

{
  "name": "Basic",
  "version": "1.0.0",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest"
  },
  "dependencies": {
    "react": "16.4.1",
    "react-native": "0.56.0",
    "react-native-today-widget": "^1.0.0"
  }
}

Next, I removed any libs that i didn't use from RNTodayWidgetExtension.xcodeproj Link Binary With Libraries Step:
Screenshot here

@kyle-ssg
Copy link
Author

kyle-ssg commented Jul 30, 2018

It seems though that even adding really basic additions to the markup cause this issue to show, unfortunately, unless this can be fixed somehow it makes the lib pretty unusable.

@jixiangyibao
Copy link

maybe my answer in #31 will help you to some extent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@kyle-ssg @jixiangyibao and others