text:
[build][cmake] Improve cmake config file generation

This allows for finding raylib on a non-standard location (eg, not in /usr/lib{,64}) when building via cmake.
The current raylib-config.cmake is a find script, not a config one.

@mobius3 Thanks for the review, it looks ok to me but I'm not a CMake expert...

@mobius3 It seems this change broke the CodeQL system:
[  9%] Linking C executable audio_mixed_processor
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_context_uninit__alsa':
raudio.c:(.text+0x3f76): undefined reference to `dlclose'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_context_uninit__pulse':
raudio.c:(.text+0x120f9): undefined reference to `dlclose'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_context_init__pulse':
raudio.c:(.text+0x25d8e): undefined reference to `dlopen'
/usr/bin/ld: raudio.c:(.text+0x25dd1): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x25e1b): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x25e65): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x25eaf): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x25ef9): undefined reference to `dlsym'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o):raudio.c:(.text+0x25f43): more undefined references to `dlsym' follow
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_context_init__pulse':
raudio.c:(.text+0x2715a): undefined reference to `dlclose'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_context_init__alsa':
raudio.c:(.text+0x27b8e): undefined reference to `dlopen'
/usr/bin/ld: raudio.c:(.text+0x27bd1): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x27c1b): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x27c65): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x27caf): undefined reference to `dlsym'
/usr/bin/ld: raudio.c:(.text+0x27cf9): undefined reference to `dlsym'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o):raudio.c:(.text+0x27d43): more undefined references to `dlsym' follow
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_dlopen':
raudio.c:(.text+0x2b16e): undefined reference to `dlopen'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_dlsym':
raudio.c:(.text+0x2b1ef): undefined reference to `dlsym'
/usr/bin/ld: ../raylib/libraylib.a(raudio.c.o): in function `ma_dlclose':
raudio.c:(.text+0x2b1b8): undefined reference to `dlclose'
/usr/bin/ld: ../raylib/libraylib.a(posix_module.c.o): in function `_glfwPlatformLoadModule':
posix_module.c:(.text+0xa): undefined reference to `dlopen'
/usr/bin/ld: ../raylib/libraylib.a(posix_module.c.o): in function `_glfwPlatformFreeModule':
posix_module.c:(.text+0x15): undefined reference to `dlclose'
/usr/bin/ld: ../raylib/libraylib.a(posix_module.c.o): in function `_glfwPlatformGetModuleSymbol':
posix_module.c:(.text+0x25): undefined reference to `dlsym'
collect2: error: ld returned 1 exit status
make[2]: *** [examples/CMakeFiles/audio_mixed_processor.dir/build.make:103: examples/audio_mixed_processor] Error 1
make[1]: *** [CMakeFiles/Makefile2:752: examples/CMakeFiles/audio_mixed_processor.dir/all] Error 2
make: *** [Makefile:[166](https://github.com/raysan5/raylib/actions/runs/12056926099/job/33620456819#step:7:167): all] Error 2

Just reverted this PR to avoid following PRs to be added over a potentially breaking change (or at least not passing CI tests)

Not sure if the issue was related but just noticed another PR: https://github.com/raysan5/raylib/pull/4547
Maybe the issue was related?


text:
Error in documentation of tocPosition ?

Describe the bug
The tocPosition parameter is shown as being under Page Parameters in the documentation, which states that page parameters are found in a post's FrontMatter.
However, looking at the implementation, e.g. in layouts/partials/sidebar/main.html
{{- if ne "content" .Site.Params.tocPosition -}}
{{- partial "sidebar/toc" . -}}
{{- end -}}

it seems that tocPosition is not a Page Parameter. It is a Site Parameter. So it should be documented in 2. Site Parameters and not in 3. Page Parameters ?
Also, it seems that the tocPosition only affects the posts layout. This should be mentioned in the documentation.

Thank you.

source: gharchive/issue

authors: razonyang sagarbehere

repo: razonyang/hugo-theme-bootstrap

license: MIT

license_type: permissive

license_source: github-api


text:
Start Up CASino

Hi there, I'm new to CASino and also in Ruby.
Before this, I search how to start CASino server after touch tmp/restart.txt but nothing happened. Then I figured out to start using command
sudo bundle exec rails s and it listen to 3000.
Where this setting written? But now, I need to start it using SSL (https). Where can I refer to setup that? And what is the recommended startup method for production CASino. Thanks

Ok. Done using apache passenger in ubuntu.

repo: rbCAS/CASino

license: mit

license_source: bigquery


text:
Installing plugin: kinnetic-scrolling

I have a problem installing

I was trying to follow..

to no avail.

Install the plugin using npm and then require (or import) it into your game app. From there, just follow the instructions at the plugin's page.
Bear in mind that this plugin isn't a CommonJS module (like many others), it'll just appear as an Phaser.Plugin 'class' after you require it.

Hint: I edited a little user's manual covering this and a few other aspects of the generator and Phaser game authoring. It's not that great but I think you'll find it useful.

thanks so much!

authors: rblopes syzer

repo: rblopes/generator-phaser-plus


text:
ASC-954 Fix Broken ZigZag Install (Master)

The interpreter directive became too long so now we need to install the venv
in a different location.
Cherry pick of #3240
Issue: ASC-954

Thank you for submitting a pull request to this project!
Once all check jobs have passed and the pull request has received a
sufficient number of reviews, the repository's gate jobs can be triggered by
adding a comment of :shipit: to this pull request.
When the gate jobs have completed successfully, this pull request will get
merged automatically.

:shipit:

source: gharchive/pull-request

authors: odyssey4me rpc-jenkins-svc ryan-rs

repo: rcbops/rpc-openstack


text:
Search for the current host in nodes

To ensure we find the current host we should search for the hostname
without domain in the response array of nodes, and then proceed to
collect metrics from that dict.
We ensure we check that the RabbitMQ version is at least 3.5.x before
checking the lengths of queues on all nodes since we know that this
check is not valid in version 3.3.5 and further noodling into the
version where that feature becomes available can be deferred based on
need.
Addresses: #610
(cherry picked from commit 78bdd1d39cd845359ac62b5a837f57439cf62cc3)

This blocks a backport of https://github.com/hughsaunders/rpc-openstack/commit/005648d6fb5005c7d788e08aa071440a0a489051

Dupe of #644


text:
🛑 Sotech is down

In c7fc3a9, Sotech (https://sotech.com.pe) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sotech is back up in 2240ad8 after 4 minutes.

repo: rclaros/pages-stack


text:
🛑 Sotech is down

In 99122dd, Sotech (https://sotech.com.pe) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sotech is back up in 0e792ad.


text:
V0.34 Update RepositoryProvider methods for obtaining list of computed-model files and bug fixes

Bug fixes:

Update getSupersededBy method to recursively return all superseded entries (resolves https://rcsbpdb.atlassian.net/browse/RO-3200)

@chrstyan Can you please review and approve these changes?


text:
Confusion due to multiple readme and license files

Hi folks,
Thank you so much for providing and maintaining this repo.
I stumbled over a series of 3 readme  and 2 license files in this repo. Do you mind reducing this series to one readme.md and one license file respectively to make clear which on is the right one?
I propose this license file.
Cheers!

Stefan,Thank you for identifying this issue and proposing a good solution. Our intent was to remain in harmony with the principles of free open source software with our initial license file, and somehow during development an additional one was added. I agree we should converge on this one, and eliminate the confusion.I will provide this to the development team so that when they complete the current security addition and update that to the repo, we converge on this one license file. The new code is installed on our beta site, and I plan to test it out this weekend.Thanks again,RobertOn Aug 11, 2023, at 4:37 AM, Stefan Begerad @.***> wrote:
Hi folks,
Thank you so much for providing and maintaining this repo.
I stumbled over a series of 3 readme  and 2 license files in this repo. Do you mind reducing this series to one readme.md and one license file respectively to make clear which on is the right one?
I propose this license file.
Cheers!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

authors: dancesWithCycles rdamashek

repo: rdamashek/Community-Through-Caring


text:
Loading model animation, there will be flickering

I don't speak English, I used a translator.
I have a problem, when loading this model, everything works fine.
However, when the specified model is loaded, the model will flicker. I tried to use the screen recording tool to record the situation encountered, but there will be no flickering in the recorded video.
So I speculate whether it is related to the frame rate of model animation.
I desperately need your help.

Sorry the provided links are unreachable

authors: leielyq rdeioris

repo: rdeioris/glTFRuntime


text:
getRadioCapabilities: reduce verbose logging

Since printf is used for logging there is no way to configure the ammount of logs printed.
getRadioCapabilities prints excesivelly each time it's called. Change that so that logs are only printed when there was an error.
Signed-off-by: Piotr Nakraszewicz piotr.nakraszewicz@consult.red
Signed-off-by: Piotr Nakraszewicz pnakraszewicz@plume.com

https://jenkins.cmf.code.rdkcentral.com/job/github-triggered/13433/ started

https://jenkins.code.rdkcentral.com/job/github-triggered/19860/ started

https://jenkins.code.rdkcentral.com/job/build-component/55103/ started.

authors: piotr-nakraszewicz-red rdkcmf-jenkins


text:
RDK-53203: Add appmanager support

Reason for change: Appmanager addition
Test Procedure: Device comes up without issue
Risks: Low
Signed-off-by: Madana Gopal Thirumalai madanagopal_thirumalai@comcast.com

b'## Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/5946/rdkcentral/rdkservices

Commit: 5a63af2a3f5757e210c54b359f7a78801def96f2

Report detail: gist'

b'## Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/5946/rdkcentral/rdkservices

Commit: ca9f89fbb1bd0c43cacb2d86070ba2c1218fa49d

Report detail: gist'

b'## Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 2 files pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/5946/rdkcentral/rdkservices

Commit: f3bb364f2b0d957220bd7b94e55d82bc3d1fce54

Report detail: gist'

b'## Blackduck scan failure details
Summary: 0 violations, 0 files pending approval, 1 file pending identification.

Protex Server Path: /home/blackduck/github/rdkservices/5946/rdkcentral/rdkservices

Commit: 0b36aa26e7c34c04e39e678177481622b07720e9

Report detail: gist'

authors: madanagopalt rdkcmf-jenkins

repo: rdkcentral/rdkservices


text:
more detailed update message during catalog import

Rationale / Begründung
An editor wants to check how the new and old version of the catalog differ.
When importing a new version of a catalog, for every existing entry a message "This element will be updated." is shown. It would be helpful if exact changes are listed during the import as well.
Affected
Managers
Minimal functionality

a more detailed information is given what is changed during the update (e.g. similar to git diff)

References / Verweise

Nearly similar to https://github.com/rdmorganiser/rdmo/issues/272
https://github.com/rdmorganiser/rdmo/issues/653

Will be part of RDMO 2.2.0.

authors: MyPyDavid jochenklar

repo: rdmorganiser/rdmo


text:
--added: Brazilian Portuguese translation (values-pt-rBR/)

Feel free to merge...
--
'Akira

Thanks, but the translations should not contain any of the "translatable=false" strings, the point of those is exactly to not need/prevent them appearing in the translations.
Also, if you can easily do it, merging it into one single commit is nicer (but doesn't matter much).

Also if you couldn't/didn't want to translate something please just leave it out so that tools detect it as missing (unless you just missed them).
Examples of what I mean:
 <VOLTA_AQUI> Dictionary location %s not writable, change in settings.
Default Dic
The directory to fired up when nothing else mentioned.

Sorry for so many comments.
I think you should also remove the translatable="false" from FreeSerif.
While it will not really be translated in most languages, there is a "translation" of it in the Japanese language file, so I think it would be incorrect to mark it this way.

Hi. Thank you for the tips. I will revise the files and return to you with a new pull request =D
--
'Akira

I think it is done, now ;)
--
'Akira

Thanks, merged.

authors: a-ira rdoeffinger

repo: rdoeffinger/Dictionary


text:
🛑 Community 方糖社区 is down

In 146ce1c, Community 方糖社区 (https://com.rdpstudio.top) was down:

HTTP code: 502
Response time: 555 ms

Resolved: Community 方糖社区 is back up in 5a6403d after 11 minutes.


text:
Add a CPFP output to the spend tx

We can reuse the same descriptor as for the unvault tx.

https://github.com/re-vault/practical-revault/issues/43


text:
reactboilerplate.com is down

React Boilerplate
Issue Type

[x] Bug (https://github.com/react-boilerplate/react-boilerplate/blob/master/.github/CONTRIBUTING.md#bug-reports)

Description
Can't open reactboilerplate.com, site is down. I tested in different browsers and connections.

Steps to reproduce
Just go to reactboilerplate.com in browser.
Versions

React-Boilerplate (see package.json):-
Node/NPM:-
Browser: Chrome 55

Works for me, can you try again? I've enabled HTTPS, so that might be why. Quick link

I saw it not working a few seconds ago. But now it's working.

Sorry for the downtime then, glad it's back up—not only that, but back up with full HTTPS! 😎

Awesome! ❤ Funny how somebody caught it right when it was down 😄

@mxstbr thanks, and pls fix link in the repo description :)

Not sure what's up with this, but I'm seeing "This site can't be reached" error for https://reactboilerplate.com/, but http://reactboilerplate.com/ is working as expected.
Chrome and Safari.

Seems to be a DNS issue when trying to use the site without the www, e.g
https://www.reactboilerplate.com/ (good)
https://reactboilerplate.com/ (broken)
It might appear to work in some browsers as the automatically prepend the www if you leave it off.
Good
http://www.reactboilerplate.com/
https://www.reactboilerplate.com/
http://react-boilerplate-site.netlify.com/
https://react-boilerplate-site.netlify.com/
Broken
http://reactboilerplate.com/
https://reactboilerplate.com/
Lookup results
https://toolbox.googleapps.com/apps/dig/#A/www.reactboilerplate.com (good)
https://toolbox.googleapps.com/apps/dig/#A/reactboilerplate.com (broken)
According to the Netlify website they recommend using the www but if you want to drop the www they recommend the following:

There are two options if you want to serve your website from a naked domain, without the www.

Recommended: Use a DNS provider that supports ANAME or ALIAS records for apex domains, and alias your naked domain to www.netlify.com. We recommend using NS1 for this purpose.
Alternative: Create an A record pointing your naked domain to our load balancer’s IP: 104.198.14.52.

I am guessing @mxstbr is the only one with the credentials to make any changes. But until he has looked into this, I would recommend changing any links to include www so it at least works when you click a link.

I clicked reopen and comment by accident, sorry. I was meant to click comment only. There only appears to be a single link to the "site" and that was in the repo description and website section which I just updated to include the www, so it works when you click the link.

Hmm, I'll look into this, thanks for digging in!

I've update the DNS records, let me know if this works?

Something has changed for sure as http://reactboilerplate.com/ is now redirecting to https://www.react-boilerplate.com/, but still doesn't appear to be working. Will test again tonight as DNS can take awhile to update properly.

Shouldn't be any issues with the name.

Sorry for not testing it earlier, but I've tried just now and this is what I found:
http://reactboilerplate.com/ - GOOD - (redirects to https://www.reactboilerplate.com/)
https://reactboilerplate.com/ - BROKEN

http://reactboilerplate.com/ - GOOD (does not redirect)
http://www.reactboilerplate.com/ - GOOD (does not redirect)
https://reactboilerplate.com/ - BROKEN
https://www.reactboilerplate.com/ - GOOD

authors: KarandikarMihir brotzky gihrig mxstbr pgrekovich samit4me

repo: react-boilerplate/react-boilerplate


text:
Unable to resolve dependency added through url

Hello,
I'm trying to add npm dependency through url.
E.g.
npm i react-redux-form
works well and this is package.json in node_moules
...
  "_args": [
    [
      {
        "raw": "react-redux-form",
        "scope": null,
        "escapedName": "react-redux-form",
        "name": "react-redux-form", //NAME POPULATED
        "rawSpec": "",
        "spec": "latest",
        "type": "tag"
      },
    ]
  ]
...

But if I add it through URL,
npm i git+ssh://git@github.com/davidkpiano/react-redux-form.git, package.json seems different and I'm unable to resolve path for 'react-redux-form':
...
  "_args": [
    [
      {
        "raw": "git+ssh://git@github.com/davidkpiano/react-redux-form.git",
        "scope": null,
        "escapedName": null,
        "name": null, //NAME IS NULL
        "rawSpec": "git+ssh://git@github.com/davidkpiano/react-redux-form.git",
        "spec": "git+ssh://git@github.com/davidkpiano/react-redux-form.git",
        "type": "hosted",
        "hosted": {
          "type": "github",
          "ssh": "git@github.com:davidkpiano/react-redux-form.git",
          "sshUrl": "git+ssh://git@github.com/davidkpiano/react-redux-form.git",
          "httpsUrl": "git+https://github.com/davidkpiano/react-redux-form.git",
          "gitUrl": "git://github.com/davidkpiano/react-redux-form.git",
          "shortcut": "github:davidkpiano/react-redux-form",
          "directUrl": "https://raw.githubusercontent.com/davidkpiano/react-redux-form/master/package.json"
        }
      },
    ]
  ]
...

I tried adding it via following commands but got same otuput.
npm install <git-host>:<git-user>/<repo-name>
npm install <tarball url>
npm install <git repo url>

Hey @jasenkoh,
npm i git+ssh://git@github.com/davidkpiano/react-redux-form.git worked for me.
Can you show that this issue is specific to react-boilerplate's setup? Did you try it with a different repo or different versions of node/npm? Closing for now as it seems more likely related to npm if anything.

authors: jasenkoh julienben


text:
Pod install errors

Hi there - this is possibly related to #184 and #250 but they've both been closed and the suggestions don't seem to make a difference.
I'm trying to install using the instructions. I get the following catch-22:
It seems like you've changed the constraints of dependency `react-native-maps` inside your development pod `react-native-maps`.
You should run `pod update react-native-maps` to apply changes you've made.
$ pod update react-native-maps
[!] The `react-native-maps` Pod is not installed and cannot be updated

(Full output log below.)
I don't know enough about Pods to say for sure but it looks like the version in NPM is still out of date. Thing is when I try npm install lelandrichardson/react-native-maps as suggested in #250  I get the same problem, and I don't know which commit to use in package.json as the podspec in master still seems to point to 0.3.1. (I could be getting the wrong end of the stick due to lack of knowledge about npm/pod/ interaction between the two.)
Is this broken, or am I just missing something? Any ideas on what to do?
Thanks!
$ node --version
v6.2.1
$ npm --version
3.9.3
$ uname -a
Darwin igors-mbp.local 15.5.0 Darwin Kernel Version 15.5.0: Tue Apr 19 18:36:36 PDT 2016; root:xnu-3248.50.21~8/RELEASE_X86_64 x86_64
$ npm install lelandrichardson/react-native-maps --save # tried "npm install react-native-maps --save", same result
$ npm install
$ rnpm link
$ cd ios
$ vi Podfile # add line: pod 'react-native-maps', :path => '../node_modules/react-native-maps'
$ cat Podfile
# Uncomment this line to define a global platform for your project
# platform :ios, '8.0'
# Uncomment this line if you're using Swift
# use_frameworks!

target 'MyApp' do
        pod 'react-native-maps', :path => '../node_modules/react-native-maps'
end

$ grep s.version ../node_modules/react-native-maps/react-native-maps.podspec
  s.version      = "0.3.1"
$ pod install
Re-creating CocoaPods due to major version update.
Analyzing dependencies
Fetching podspec for `react-native-maps` from `../node_modules/react-native-maps`
[!] Unable to satisfy the following requirements:

- `react-native-maps (from `../node_modules/react-native-maps`)` required by `Podfile`

It seems like you've changed the constraints of dependency `react-native-maps` inside your development pod `react-native-maps`.
You should run `pod update react-native-maps` to apply changes you've made.
$ pod update react-native-maps
[!] The `react-native-maps` Pod is not installed and cannot be updated
$ cat Pods/Local\ Podspecs/react-native-maps.podspec.json
{
  "name": "react-native-maps",
  "version": "0.3.1",
  "summary": "React Native Mapview component for iOS + Android",
  "authors": {
    "intelligibabble": "leland.m.richardson@gmail.com"
  },
  "homepage": "https://github.com/lelandrichardson/react-native-maps#readme",
  "license": "MIT",
  "platforms": {
    "ios": "8.0"
  },
  "source": {
    "git": "https://github.com/lelandrichardson/react-native-maps.git"
  },
  "source_files": "ios/AirMaps/**/*.{h,m}",
  "dependencies": {
    "React": [

    ]
  }
}
$ cat ../package.json
{
  "name": "MyApp",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start"
  },
  "dependencies": {
    "react": "15.0.2",
    "react-mixin": "^3.0.5",
    "react-native": "0.26.2",
    "react-native-maps": "github:lelandrichardson/react-native-maps",
    "react-redux": "^4.4.5",
    "react-timer-mixin": "^0.13.3",
    "redux": "^3.0.0",
    "redux-actions": "^0.9.1"
  },
  "devDependencies": {
    "rnpm-plugin-upgrade": "^0.26.0"
  }
}

Running into this very thing. Were you able to find a solution?

Hey @erickreutz, no, I gave up in the end. I found the same problem trying to use another React Native module that linked native code via a Pod.
However, I did manage to get the Mapbox native component installed via CocoaPods and successfully exposed the basics of that to React as Native UI Component. So I'm left wondering if it's a problem with [i] these projects; [ii] my Mac/setup; [iii] rnpm; [iv] pod. My guess is [iii]. (Or of course [ii] ;-)).
Would love to know if you work out how to get around this!

Encountering this as well.  https://github.com/lelandrichardson/react-native-maps/pull/308 appears to be related.

having the same issue. anyone already found a workaround?

uncommenting "platform :ios, '9.0'" at second line of generated Podfile will solve the problem :)

having the same issue:
$ pod install
Analyzing dependencies
Fetching podspec for `react-native-maps` from `../node_modules/react-native-maps`
[!] Unable to satisfy the following requirements:

- `react-native-maps (from `../node_modules/react-native-maps`)` required by `Podfile`

It seems like you've changed the constraints of dependency `react-native-maps` inside your development pod `react-native-maps`.
You should run `pod update react-native-maps` to apply changes you've made.

reproduce:

react-native init newproject
Follow instructions exactly as they are are on react-native-maps README
arrive at the part where I pod install and run pod install
above error occurs

Using platform :ios, '9.0' fixed this for me...

Ran into a similar issue. After installing cocoapods (sudo gem install cocoapods) generating a Podfile (cd ios && touch Podfile) and by adding the following to Podfile swapping NAME_OF_PROJECT with the project name
platform :ios, '9.0'
workspace './NAME_OF_PROJECT.xcodeproj/project.xcworkspace'

target 'NAME_OF_PROJECT' do
  pod 'react-native-maps', :path => '../node_modules/react-native-maps'
end

.. Then run pod install inside the ios directory and you should be good to go

# Uncomment this line to define a global platform for your project
platform :ios, '8.0'

It seems that platform must be declared in Podfile,and the Value must be greater than or equal to 8.0

I recently made a fresh example build with pods and GoogleMaps with no issues.
https://github.com/alvelig/react-native-maps-pods-example.
Try to check it out or build through the README.MD. If it does not help, let me know.

authors: PotterDai alvelig benmarten brianjd charliesbox erickreutz igorclark ios122 masterkrang nsarafa

repo: react-community/react-native-maps


text:
Navigate not working to screens with tab visibility: false

Hi,
New to both react-native and react-navigation so it might be me doing something wrong :o,
When i call navigate('LoginStack') where the nested screen has the prop:
static navigationOptions = {
title: 'Login',
tabBar: {
visible: false
}
}
It navigates to an empty screen, while if i set visible to true it shows the content correctly? The content also shows correctly with the false setting on the initialRoute which is set to the LoginStack. It's only when i click logout and navigate back to the LoginStack that the problem arises and as mentioned only if tabBar>visible=false.

I met the same problem.

I cope it.
Home: { screen: Wrapper, navigationOptions: {headerMode: 'screen', header: {visible: false}}},

const navigator = StackNavigator({
  Home: { screen: Wrapper, navigationOptions: {header: {visible: false}}},
  DetailPage: { screen: DetailPage }
},{
    headerMode: 'screen'
  });

may help you

Yeah, ended up doing something similar with:
export const Tabs = TabNavigator({
TripsScreen: {
screen: TripsScreen,
},
MapScreen: {
screen: MapScreen
},
DirectionsScreen: {
screen: DirectionsScreen,
}
}, {
headerMode: 'card',
swipEnabled: true,
tabBarOptions: {
showIcon: true,
showLabel: false,
upperCaseLabel: false,
inactiveTintColor: CommonStyles.colorAccentText,
activeTintColor: CommonStyles.colorAccentText,
pressColor: CommonStyles.colorAccent20P,
style: {
backgroundColor: CommonStyles.colorPrimary700,
paddingVertical: 5,
},
indicatorStyle: {
backgroundColor: CommonStyles.colorAccent
}
}
}
);
export const Root = StackNavigator({
LoginScreen: {
screen: LoginScreen
},
Tabs: {
screen: Tabs
}
},
{
headerMode: 'screen'
}
);

Sounds like you were able to resolve it. Please provide more example code next time, otherwise it will be very difficult to help

authors: NielsLindberg ericvicenti jerossh

repo: react-community/react-navigation


text:
Fix autolink on react-native 0.60 or higher

Summary
Add react-native-cookies.podspec on npm to react-native autolink work as expected
Test Plan
Install this package in react-native that uses react-native 0.60 or higher and go to ios folder an run pod install and the package should be linked automatically
What's required for testing (prerequisites)?
Use react native 0.60 or higher
What are the steps to reproduce (after prerequisites)?
run pod install in current version and the package doesn't linked automatically
Compatibility

OS
Implemented

iOS
✅

Android
❌

Checklist

[X] I have tested this on a device and a simulator
[ ] I added the documentation in README.md
[ ] I mentioned this change in CHANGELOG.md
[ ] I updated the typed files (TS and Flow)
[ ] I added a sample use of the API in the example project (example/App.js)

Thanks @luancurti there's a podspec file in the iOS folder, could you delete that as well

Thanks @luancurti there's a podspec file in the iOS folder, could you delete that as well

I removed see

Ahh missed it, thanks!

authors: luancurti safaiyeh

repo: react-native-community/cookies


text:
Animation does not show

Description
Animation is not visible/is not showing
Steps to Reproduce

install lottie-ios@2.5.0
install lottie-react-native@2.6.1
use any sample JSON animation

Expected behavior:
animation renders on screen
Actual behavior: [What actually happened]
animation was not displayed
Versions
npm: '6.4.1',
ares: '1.14.0',
cldr: '33.1',
http_parser: '2.8.0',
icu: '62.1',
modules: '64',
napi: '3',
nghttp2: '1.34.0',
node: '10.13.0',
openssl: '1.1.0i',
tz: '2018e',
unicode: '11.0',
uv: '1.23.2',
v8: '6.8.275.32-node.36',
zlib: '1.2.11' }
react native info:
System:
OS: macOS 10.15.3
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Memory: 11.18 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 10.13.0 - /usr/local/bin/node
npm: 6.4.1 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK:
API Levels: 23, 25, 26, 27, 28
Build Tools: 26.0.1, 27.0.3, 28.0.3
System Images: android-22 | Google APIs Intel x86 Atom_64, android-23 | Google APIs Intel x86 Atom_64, android-25 | Intel x86 Atom_64, android-25 | Google APIs Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-27 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5977832
Xcode: 11.2.1/11B500 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.3 => 16.8.3
react-native: 0.59.1 => 0.59.1
npmGlobalPackages:
create-react-native-app: 2.0.2
react-native-cli: 2.0.1
code snippet:
<LottieView style={{
            position: 'absolute',
            zIndex: 100,
            top: '16%',
            left: '12%',
            height: '10%',
            width: '10%',
          }} source={NewAnimation} autoPlay loop />

forgot to mention that my code runs just fun and I'm able to start up the app on IOS. I just don't see the animation that I'm using at all. I should mention that I'm also using a sample animation from Lottie files.

I also tried installing the following versions as described in the docs for RN 0.59:
npm i --save lottie-react-native@3.0.2
npm i --save lottie-ios@3.0.3
and following the installation steps, and still nothing is showing up.

I'm also importing New Animation at the top of my file like so:
import NewAnimation from '../images/animations/newAnimations/19507-pc-to-phone.json';

If you are using Android just try to rebuild the app from Android Studio. Fixxed my issues I had with lottie.

you try add this on package.json
"lottie-react-native":"git+ssh://git@gitlab.com:cohedz/lottie-react-native.git"
in podfile
pod 'lottie-ios', '~> 2.5.3'
pod 'lottie-react-native', :path => '../node_modules/lottie-react-native'

I solved this by just upgrading to the latest version of React Native (0.62.2) and installing lottie-react-native and lottie-ios@3.1.3


text:
App crashes on iOS for local video uri

The uri returned for video is uri for the video's thumbnail not the video itself, and as a result the app freezes/crashes.

A solution that I found is to use react-native-gallery-manager, it returns AVAsset uri for videos instead of unplayable PHAsset uri returned by react-native-cameraroll

Thanks for reporting, we'll have a look!

I got the same error! RN 0.59.3 and iOS 12.2!

@bartolkaruza Hi,
Did you take a look ? Because PHAsset are just not compatible with any library like RNFS / Fetch BLOB or so, we just can't use this simply. Is it possible to bring back some assets-library path ?

@jonathangreco I'm struggling to find the time to implement bigger changes like that one. In the mean time, have you seen the workaround for #52 here: https://github.com/react-native-community/react-native-cameraroll/issues/52#issuecomment-488601591
I think implementing a conversion by default inside Cameraroll would be the way to go.

@bartolkaruza Yes I've implemented it. Sure it works but for how long ? Some people find that not stable, me too.

https://github.com/jzyds/react-native-convert-ph-asset

Closing this, for now, see workarounds above if you experience this issue. We'll look at a better handling of the ph url's in one go, hopefully soon.

authors: bartolkaruza emilemoureau jonathangreco jzyds ramon90


text:
Return a HTTPS url rather than a File URL

I need to pass a website url to my firebase authentication but currently the ImagePicker function returns a file URL. And there is no usable way for me to convert a file URL to a website url. So I was wondering if there was any way for imagepicker to return a website/HTTPS url. I'm not exactly sure how to do it or if there already exists a way but I thought I'd put this out there.

You first need to upload the image returned by the ImagePicker to a web service where you can retrieve the image back with an HTTPS url.

Get image from picker
Upload to web storage, can be your own web server or Firebase's Cloud Storage
Return the HTTPS url for that image, Firebase should have docs on this
Pass that URL to your Firebase Authentication

Hope that helps you out!

authors: RigoTheDev ruthvikkonda


text:
Screen not translate when side menu open.

I want screen not translate to left or right when side menu open like drawer menu. Anyone help me?

+1


text:
Added feature to not relay on having commas for Polygons points to work

Currently Polygon.js only accepts points with comma format, like:
<Polygon points="40,5 70,80 25,95"/>
This PR includes the possibility to write points as you wish (with commas, without or misc):
E.g:
<Polygon points="40 5   70,80 25 95"/>
<Polygon points="40   5 70   80 25        95"/>
<Polygon points="40,5 70,80 25,95"/>

@magicismight can you please review?

Thanks for this PR 👍
But I have to close this now.
This had been fixed in https://github.com/react-native-community/react-native-svg/pull/298/commits/e3b2f4c71add751c29eaa572bb8f0555aca305fb

authors: magicismight thalescm

repo: react-native-community/react-native-svg


text:
"X-Content-Type: nosniff" was given and its Content-Type is not a script MIME type.

Bug description:
I have a problem with WebView on React Native Expo project.
I have a WebView like this:
 <WebView
	originWhitelist={['*']}
	nativeConfig={{props: {webContentsDebuggingEnabled: true}}}
	ref={webview => { this.myWebView = webview;	}}
	source={require('./Resources/indexSummary.html')}
	javaScriptEnabled={true}
	injectedJavaScript={patchPostMessageJsCode}
	onMessage={this.onWebViewMessage}
/>

The indexSummary.html is:

When I display WebView, I have these errors:
[Error] Refused to execute http://127.0.0.1:19001/assets/src/Graphics/TitleDetail/TVChart/Resources/Utils.js as script because "X-Content-Type: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://127.0.0.1:19001/assets/src/Graphics/TitleDetail/TVChart/Resources/WebViewBridge.js as script because "X-Content-Type: nosniff" was given and its Content-Type is not a script MIME type.
[Error] Refused to execute http://127.0.0.1:19001/assets/src/Graphics/TitleDetail/TVChart/Resources/TVScriptSummary.js as script because "X-Content-Type: nosniff" was given and its Content-Type is not a script MIME type.

Probably this issue is related to Expo content-type returned value.
To Reproduce:
Load a Webview into blank react-native project created by expo
Environment:

OS: macOS Mojave
OS version: 10.14.5
react-native version: 33.0.0
react-native-webview version: 5.8.1

Looks like related: https://github.com/facebook/metro/issues/368

authors: pZambotti yatagan


text:
npm install instructions to docs

Update instructions for npm

Thank you @a-c-sreedhar-reddy !

authors: a-c-sreedhar-reddy jamonholmgren


text:
Possibility of fixed marker and draggable map

This is pretty similar to how Uber behaves.
Instead of dragging the map marker (which is not necessarily a good ux), uber allows to drag the map while the pin is fixed in the middle of the screen.

Assuming your MapView is filling whatever view it's in, you can just put another view with only your marker in the center of it over the MapView. I'm doing this right now by putting the following right after my MapView. Then you can just use the MapView methods to get its current location.
<View pointerEvents="none" style={{position: 'absolute', top: 0, bottom: 0, left: 0, right: 0, alignItems: 'center', justifyContent: 'center', backgroundColor: 'transparent'}}>
    <Image pointerEvents="none" source={markerImage}/>
</View>

sounds like a solution, although Ideally it would be nice to have something passed to marker to make it static on the screen instead of the map.
In your case, do you use screen resolutions, map width/height to get the lat/long value or is there a better way?

If you pass it to a marker it will be static with respect to the map, that's the point of a marker. It's a child of the map, so as you drag the map the marker gets dragged too. What you want is something completely independent of the map.
Use the MapView method onRegionChange and update a state variable that you can then use to figure out where the center of the map and thus your marker is.

@ahmed1490
@heydabop Is right that want you are looking for is something independent. I would also suggest using onRegionChange to achieve what your looking for.

But what if you need to have draggable map? View with your marker icon will cover MapView, so I won't respond to dragging events.

@b4lk0n as in the example above, using the 'pointerEvents="none"' prop fixes that issue

Assuming your MapView is filling whatever view it's in, you can just put another view with only your marker in the center of it over the MapView. I'm doing this right now by putting the following right after my MapView. Then you can just use the MapView methods to get its current location.
<View pointerEvents="none" style={{position: 'absolute', top: 0, bottom: 0, left: 0, right: 0, alignItems: 'center', justifyContent: 'center', backgroundColor: 'transparent'}}>
    <Image pointerEvents="none" source={markerImage}/>
</View>

Using this approach I can no longer drag map.

repo: react-native-maps/react-native-maps


text:
fatal error: 'RNKakaoLogins.h' file not found 에러

Version of kakao-login libraries
3.3.3
Version of react-native
0.61.5
Platforms you faced the error (IOS or Android or both?)
iOS
Expected behavior
정상 빌드
Actual behavior
AppDelegate.m 파일에서 README에 있는대로
#import <RNKakaoLogins.h>
...
- (BOOL)application:(UIApplication *)application openURL:(NSURL *)url
                                       sourceApplication:(NSString *)sourceApplication
                                              annotation:(id)annotation {
    if([RNKakaoLogins isKakaoTalkLoginUrl:url]) {
      return [RNKakaoLogins handleOpenUrl: url];
    }

    return NO;
}

를 추가하고 빌드했을때
AppDelegate.m:28:9: fatal error: 'RNKakaoLogins.h' file not found
#import <RNKakaoLogins.h>
위 에러가 발생합니다.
Tested environment (Emulator? Real Device?)
에뮬레이터, 단말 모두 해당 에러가 발생합니다.
기존에 3.0.2 버젼을 사용하면서  AppDelegate.m  쪽 코드는 따로 수정하지 않았었는데
이번에 카카오톡이 설치되어있으면 로그인이 안되는 이슈가 발생하여 3.3.3 버전으로 업데이트 후 README대로 수정하다가 에러가 발생했습니다.
혹시 몰라 삭제 후 재설치 해봐도 동일합니다.

자답입니다.
Pod 폴더 삭제하고 재설치 하니 정상 동작되네요^^


text:
[iOS] baseUrl not working. local image is not showing up.

Bug description:
I use the code below to display a local image to Webview.
const imagePath = `${RNFS.DocumentDirectoryPath}/${new Date().toISOString()}.jpg`.replace(/:/g, '-');
const html = `<img src="${imagePath}" style="position: relative; max-width: 100%; max-height: 100%;"/>`;

<WebView
    originWhitelist={['*']}
    allowUniversalAccessFromFileURLs={true}
    allowFileAccessFromFileURLs={true}
    allowFileAccess={true}
    source={{
        html,
        baseUrl: 'file://',
    }}
/>

And it works perfectly on Android(emulator, device) and iOS(simulator).
However, not work on iOS device.
the image exists. I can display it with the code below on RN.
<Image
    style={{width: 250, height: 250,}}
    source={{
        uri: Platform.OS === 'ios' ?
            imagePath
            : `file://${imagePath}`,
    }}
/>

To Reproduce:
I couldn't find

Expected behavior:
the image is displayed on iOS device.

Screenshots/Videos:

Environment:

react-native version: 0.61.5
react-native-webview version: 8.0.4

this component seems unusable but I don't find any alternatives.  I cannot make it work on iOS either.  I've tried numerous ways as recommended on various postings but without success.  I'm on the latest versions of everything

The same issue facing with all latest version, I need community support and help to fix it.

Same problem here. Using a react app inside a react-native-webview images are displayed on simulator but not on real iOS device.

I have found a solution for local images rendering in react-native-webview in iOS.
convert the image in base64 then used it's working fine on all iOS devices.
const fs = RNFetchBlob.fs
const imageData = await fs.readFile(${imageLocalPath}, 'base64')
const htmlStr =
return (<WebView
originWhitelist={['*']}
source={{ htmlStr }}
/>)

I have the same problem, only instead of an image it's an html file (previously created in React). Has anyone been able to solve this?

I have the same problem, only instead of an image it's an html file (previously created in React). Has anyone been able to solve this?

I have the same problem, only instead of an image it's an html file (previously created in React). Has anyone been able to solve this?

the joys of open-source, where an issue never gets any love.  I eventually gave up on this

I have the same problem, only instead of an image it's an html file (previously created in React). Has anyone been able to solve this?

the joys of open-source, where an issue never gets any love.  I eventually gave up on this

@ambreesh , i am facing similar issue, could you please post your complete answer?
Where should i add image in iOS?

I'm currently facing this issue, everything works perfectly on the iOS simulator but on an actual iOS device, no images/css/js files are being correctly resourced by the HTML file.

I have the same problem ， any update

authors: PaulPourtout ambreesh dev-yakuza ekkis gebo96 leandronorcio pallaviMN suwu150


text:
Unable to load local file on Android

When trying to open a local webpage from tyhe local file system (using file://) it works on iOS, but on Android we get an error:
Encountered an error loading page:
{
  canGoBack: false,
  canGoForward: false,
  code: -1,
  description: "net::ERR_ACCESS_DENIED",
  loading: false,
  target: 165,
  title: "Webpagina niet beschikbaar",
  url: "file:///data/user/0/com.twipepocv4/cache/data/36/Page-313.html",
}

This is my code:
      <WebView
        originWhitelist={['*']}
        allowFileAccess={true}
        source={{uri: "file:///data/user/0/<myapp>/cache/data/36/Page-319.html"}}
        domStorageEnabled={true}
        allowUniversalAccessFromFileURLs={true}
        allowFileAccessFromFileURLs={true}
      />

I believe this has something to do with AllowFileAccessFromFileURLs but I can't get it to work.
Should any other permission be set?

I'm also seeing this error. It started happening when we upgraded to react native 0.59. Could this be related? https://github.com/expo/expo/issues/2402#issuecomment-443726662

Facing the same error from time to time

You guys are not doing properly,
Proper ways is as follows:
First install it using (If not installed),
npm install --save react-native-webview // inside project root directory
react-native link react-native-webview // it will link WebView with iOS and Android
import React, { Component } from 'react';
import { WebView } from 'react-native-webview';
import {LocalHtml} from './project-root/html/demo.html'; // path of your file starts with "./"

class MyInlineWeb extends Component {
  render() {
    return (
      <WebView
        originWhitelist={['*']}
        source={{ html: LocalHtml }} // here it will render your html content and load on webview.
        javaScriptEnabled={true}
        domStorageEnabled={true}
        useWebKit={true}
        startInLoadingState={true}

      />
    );
  }
}

I hope this will help you guys.

So I ran into the same issue. What solved it for me was to add the prop allowFileAccess in the WebView (and also don't forget to ask the permission READ_EXTERNAL_STORAGE)

So I ran into the same issue. What solved it for me was to add the prop allowFileAccess in the WebView (and also don't forget to ask the permission READ_EXTERNAL_STORAGE)

It doesn't require to use prop "allowFileAccess", you try above code, it will work perfectly.

You guys are not doing properly,
Proper ways is as follows:
First install it using (If not installed),
npm install --save react-native-webview // inside project root directory
react-native link react-native-webview // it will link WebView with iOS and Android
import React, { Component } from 'react';
import { WebView } from 'react-native-webview';
import {LocalHtml} from './project-root/html/demo.html'; // path of your file starts with "./"
_// as per above example replace it with above LocalHtml_
_//import {LocalHtmlText} from './data/user/0/com.twipepocv4/cache/data/36/Page-313.html';_

class MyInlineWeb extends Component {
  render() {
    return (
      <WebView
        originWhitelist={['*']}
        source={{ html: LocalHtml }} // here it will render your html content and load on webview.
        javaScriptEnabled={true}
        domStorageEnabled={true}
        useWebKit={true}
        startInLoadingState={true}

      />
    );
  }
}

I hope this will help you guys.

What if your path to the html is dynamic? And you don't know the exact file path at build.

@femiveys
Navigate to node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
Change the following lines:

settings.setAllowFileAccess(true);
settings.setAllowContentAccess(true);
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN) {
    settings.setAllowFileAccessFromFileURLs(true);
    setAllowUniversalAccessFromFileURLs(webView, true);
}

By default, these props will be false, make it true and you're good to go. :)

You guys are not doing properly,
Proper ways is as follows:
First install it using (If not installed),
npm install --save react-native-webview // inside project root directory
react-native link react-native-webview // it will link WebView with iOS and Android
import React, { Component } from 'react';
import { WebView } from 'react-native-webview';
import {LocalHtml} from './project-root/html/demo.html'; // path of your file starts with "./"
_// as per above example replace it with above LocalHtml_
_//import {LocalHtmlText} from './data/user/0/com.twipepocv4/cache/data/36/Page-313.html';_

class MyInlineWeb extends Component {
  render() {
    return (
      <WebView
        originWhitelist={['*']}
        source={{ html: LocalHtml }} // here it will render your html content and load on webview.
        javaScriptEnabled={true}
        domStorageEnabled={true}
        useWebKit={true}
        startInLoadingState={true}

      />
    );
  }
}

I hope this will help you

@mayursarode4
What if your path to the html is dynamic? And you don't know the exact file path at build.

I tried this. But got Empty white screen.
I need to render a html page which import local assests and javascript code in it.

I also encountered the same problem @imran1992
expo: v34.0.1 react-native-webview: v5.12.0 expo-cli: v3.0.4

I also encountered the same problem @imran1992
expo: v34.0.1 react-native-webview: v5.12.0 expo-cli: v3.0.4

Try above solution by @imran1992 it will help you solve your issue
for react-native: 0.60.+ version's doesn't require linking for libraries as it have auto linking feature, you just need to install the libraries and build and run the project.
My version details are,
react-native info
info Fetching system and libraries information...
System:
OS: Linux 4.4 Ubuntu 16.04.6 LTS (Xenial Xerus)
CPU: (4) x64 Intel(R) Core(TM) i5-4440S CPU @ 2.80GHz
Memory: 8.86 GB / 15.57 GB
Shell: 4.3.48 - /bin/bash
Binaries:
Node: 12.4.0 - ~/.nvm/versions/node/v12.4.0/bin/node
npm: 6.9.0 - ~/.nvm/versions/node/v12.4.0/bin/npm
SDKs:
Android SDK:
API Levels: 21, 22, 23, 25, 26, 27, 28
Build Tools: 21.1.2, 25.0.0, 25.0.2, 25.0.3, 27.0.3, 28.0.2, 28.0.3
System Images: android-25 | Google Play Intel x86 Atom, android-28 | Intel x86 Atom, android-28 |Intel x86 Atom_64
IDEs:
Android Studio: 3.4 AI-183.6156.11.34.5692245
npmPackages:
react: 16.8.6 => 16.8.6
react-native: 0.60.4 => 0.60.4
npmGlobalPackages:
react-native-cli: 2.0.1
I'm not using expo-cli, so don't know about it

There is only one solution for me.
I convert all the local assets into 'base64'
And use that base64 string as sourece for img, mp3 and even JavaScript file. And past whole html into source of webview. And it work.
I mean source={{html:`.......}}
And the whole string become 3MB file.....

It works 50/50. Sometimes my locally storaged html renders and sometimes I get ACCESS_DENIED error. Is there any solution?

Hi,
I've managed to load a local, downloaded file stored at  /Users/rotoxl/Library/Developer/CoreSimulator/Devices/987C6DE3-29BB-4197-B22E-DC4A550C9E40/data/Containers/Data/Application/A0BAD256-CCBE-4F89-A1DB-D635F6532A57/Documents/course123/lesson320/file.html.
Please read the complete answer at issues/746#issuecomment-524291199

@Shan7anu said:

Navigate to node_modules/react-native-webview/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java
Change the following lines:

settings.setAllowFileAccess(true);
settings.setAllowContentAccess(true);
if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.JELLY_BEAN) {
    settings.setAllowFileAccessFromFileURLs(true);
    setAllowUniversalAccessFromFileURLs(webView, true);
}

By default, these props will be false, make it true and you're good to go. :)

While this is not a fix that I would be comfortable putting into my production code, it does point to the underlying problem, which is that the order in which the WebView props are set may not be deterministic. I added System.out.println calls to the setSource and setAllowFileAccess methods in RNCWebViewManager.java (version 6.11.1), and when the WebView failed to load the local file URL, it was clear that the setSource method was called before setAllowFileAccess was called, so the page was being loaded before the allowFileAccess prop was applied.
It seems like there needs to be a mechanism to store the prop values but not actually call loadUrl/loadDataWithBaseURL until after all props have been stored and their settings have been applied to the WebSettings object for the current WebView instance.

@tjensen is exactly right.
Problem
react-native-webview on Android handles the allowFileAccess
and allowUniversalAccessFromFileURLs by calling
view.getSetings().setAllowFileAccess() in the Java code:
https://github.com/react-native-community/react-native-webview/blob/47e9a0b/android/src/main/java/com/reactnativecommunity/webview/RNCWebViewManager.java#L484
At the same time, setting source calls view.loadUrl(). This results
in a race where if view.loadUrl() executes before the security settings
are updated, the page-load will fail.
Workaround
We don't load your local file until we're sure the correct permissions have been set on the WebView.
On the component you have that renders <WebView source={...}>:

Create a state variable in the constructor or the class

this.state = { renderedOnce: false };

In componentDidMount, set that variable to be true

componentDidMount() {
  this.setState({ renderedOnce: true });
}

When rendering, render your file only when renderedOnce is true:

render() {
  return <WebView source={renderedOnce ? { uri: indexHtmlPath } : undefined} />;
}

@hsource Thank you so much! I've done so much research to try and fix this issue and this is the only thing that works. Much appreciated!! :D

I use functional components and had no luck with replacing the componentDidMount with a useEffect.  However, I got the solution from @hsource to work by updating the setRenderedOnce  in a function that I pass to the webview's onLoad prop:

const [renderedOnce, setRenderedOnce] = useState(false);

const updateSource = () => {
    setRenderedOnce(true);
 };

<WebView
    originWhitelist={['*']}
    source={renderedOnce ? {uri: localHTML} : undefined}
    style={{flex: 1}}
    allowFileAccess={true}
    allowUniversalAccessFromFileURLs={true}
    allowingReadAccessToURL={workingDir}
    onLoad={updateSource}
/>

This issue should remain reopen

This is my working solution - integration of fusioncharts for Android and IOS with React Native + EXPO!
import FusionCharts from "react-native-fusioncharts";
import * as FileSystem from "expo-file-system";
import { Asset } from "expo-asset";
const [htmlPage, setHtmlPage] = useState(null);
const getHTML = useCallback(async () => {
const indexHtml = Asset.fromModule(
require("../../../assets/fusioncharts.html")
);
await indexHtml.downloadAsync();
const HTMLFile = await FileSystem.readAsStringAsync(indexHtml.localUri);
setHtmlPage(HTMLFile);
}, []);
useEffect(() => {
getHTML();
}, [getHTML]);
return (
....
{htmlPage != null && (
<FusionCharts
type={state.type}
width={state.width}
height={state.height}
dataFormat={state.dataFormat}
dataSource={state.dataSource}
libraryPath={{ html: htmlPage }}
/>
)}
....
);

@yaoonline can you please post the entire code? This seems not working to me. Thanks

I still get an error on android, @femiveys did you manage to get it working?

I only use hooks and no classes, so use useEffect and useCallback in this way!
This code works for displaying local HTML pages on both IOS and Android.
import React, { useState, useEffect, useCallback } from 'react';
import { StyleSheet, View } from 'react-native';
import FusionCharts from 'react-native-fusioncharts';
import * as FileSystem from 'expo-file-system';
import { Asset } from 'expo-asset';
....... here different code does not concern the main idea of the solution
const [libraryPath, setLibraryPath] = useState(null);
const getLibraryPath = useCallback(async () => {
const indexHtml = await Asset.fromModule(
require('../../../../assets/fusioncharts.html')
).downloadAsync();
return await FileSystem.readAsStringAsync(indexHtml.localUri);
});
useEffect(() => {
async function setData() {
Promise.all([dataFetch, schemaFetch]).then(async (res) => {
setState({ ...state, dataJson: res[0], schemaJson: res[1] });
setLibraryPath({ html: await getLibraryPath() });
});
}
setData();
}, []);
return (

);

thank you for your reply @yaoonline !

I tried all solutions suggested above, but ERR_ACCESS_DENIED problem occurs. In my case, I download and save a file to my app's cache directory (e.g. file:///data/user/0/.../cache/5f8f.../downloaded.pdf) and try to open this file using WebView. My WebView code is:
<WebView
  source={{ uri: file.uri }}
  startInLoadingState
  originWhitelist={['file://']}
  allowUniversalAccessFromFileURLs={true}
  allowFileAccess={true}
/>

On iOS, it works fine. However, on Android, it prints ERR_ACCESS_DENIED.
I've tried the solution put renderOnce state but it did not work for me.
Any other solution to solve my problem? Thanks, in advance. If you need more code to investigate, please let me know.

This worked with a local uri like this (only tested in dev) :
import {useAssets} from 'expo-asset';
import {Platform} from 'react-native';
import {WebView} from 'react-native-webview';
...
  const [assets] = useAssets([require('../../../assets/myhtml.html')]);
  const htmlAsset = assets?.[0];
...
      <WebView
        source={
          htmlAsset
            ? {
                uri:
                  Platform.OS === 'android'
                    ? htmlAsset.localUri
                    : htmlAsset.uri,
              }
            : undefined
        }
        onMessage={event => {
          console.log(JSON.parse(event.nativeEvent.data));
        }}
        startInLoadingState={true}
        originWhitelist={['*']}
        allowFileAccess={true}
        allowUniversalAccessFromFileURLs={true}
      />
...

Using expo-asset and this trick : https://github.com/react-native-webview/react-native-webview/issues/656#issuecomment-551312436

I am trying below but no luck
`render() {
return (

<WebView
allowFileAccessFromFileURLs={true}
allowFileAccess={true}
bounces={false}
scrollEnabled={false}
source={{ uri:"file:///android_asset/pdf/sample.pdf",baseUrl:"file:///android_asset/pdf/"}}
/>
    </View>
  );
}

`
Any Suggestions?

@developeromI89 if you only want to open PDFs you can use '[react-native-view-pdf](https://www.npmjs.com/package/react-native-view-pdf)'
Or you can use append your WebView url like this:
"https://docs.google.com/gview?embedded=true&url=$url"

I use functional components and hooks and got the solution from @hsource to work by updating the setRenderedOnce  in a function that I pass to the webview's onLoad prop:
const [renderedOnce, setRenderedOnce] = useState(false);

const updateSource = () => {
    setRenderedOnce(true);
 };

return(
   <WebView
       originWhitelist={['*']}
       source={renderedOnce ? {uri: localHTML} : undefined}
       style={{flex: 1}}
       allowFileAccess={true}
       allowUniversalAccessFromFileURLs={true}
       onLoad={updateSource}
   />)

For new versions, you have to change it for:
source={renderedOnce ? {uri: localHTML} : { uri: null }}

this still an issue - should be open.

I'm having a similar issue.
We use react native and webview to a react web app.
We get intermitted failures on file uploads on Android only.
So a user wants to change their headshot, by tapping the  element in the webview.
it pop up the media picker a file object is returned and then we try to uploaded it to our servers. But for the same file, over and over again, we get an error reading the file. But the error is not helpful its just an object that say { isTrusted: true }.

I use functional components and hooks and got the solution from @hsource to work by updating the setRenderedOnce  in a function that I pass to the webview's onLoad prop:
const [renderedOnce, setRenderedOnce] = useState(false);

const updateSource = () => {
    setRenderedOnce(true);
 };

return(
   <WebView
       originWhitelist={['*']}
       source={renderedOnce ? {uri: localHTML} : undefined}
       style={{flex: 1}}
       allowFileAccess={true}
       allowUniversalAccessFromFileURLs={true}
       onLoad={updateSource}
   />)

For new versions, you have to change it for:
source={renderedOnce ? {uri: localHTML} : { uri: null }}

This still threw me an error. It seem that the onLoad method does not get triggered
My solution was this:
source={renderedOnce ? {uri: htmlPath}: {html: '

'}}
First I render just and empty html (div) and then the onLoad gets triggered and then load the actual HTML

authors: ALEEF02 AlexUzan Shan7anu byron1st developeromI89 elliotstokes femiveys hrtest-dev hsource imran1992 jstnbchnn judare kristensala lapico markalanevans mayursarode4 meabed rotoxl sirmong stephenkopylov sunnylqm tjensen vgorte yaoonline zhouping3


text:
Fix small syntax mistake

Missing a =

thanks!

authors: johanforslund vonovak


text:
Menu cropped when embedded in a NavDrawer in a Layout

class LayoutTest extends React.Component {
    state = {
        drawerActive: false,
        drawerPinned: false,
        sidebarPinned: false
    };

    toggleDrawerActive = () => {
        this.setState({ drawerActive: !this.state.drawerActive });
    };

    toggleDrawerPinned = () => {
        this.setState({ drawerPinned: !this.state.drawerPinned });
    }

    toggleSidebar = () => {
        this.setState({ sidebarPinned: !this.state.sidebarPinned });
    };

    render() {
        return (
            <Layout>
                <NavDrawer pinned={true}>
                    <AppBar title="Hello">
                    	<IconMenu icon='more_vert' position='topLeft' menuRipple>
                        <MenuItem value='download' icon='get_app' caption='Download' />
                        <MenuItem value='help' icon='favorite' caption='Favorite' />
                        <MenuItem value='settings' icon='open_in_browser' caption='Open in app' />
                        <MenuDivider />
                        <MenuItem value='signout' icon='delete' caption='Delete' disabled />
                      </IconMenu>
                    </AppBar>
                </NavDrawer>
                <Panel>
                    <AppBar leftIcon='menu' onLeftIconClick={ this.toggleDrawerActive } />

Main Content

Main content goes here.

                        <Checkbox label='Pin drawer' checked={this.state.drawerPinned} onChange={this.toggleDrawerPinned} />
                        <Checkbox label='Show sidebar' checked={this.state.sidebarPinned} onChange={this.toggleSidebar} />

                </Panel>
                <Sidebar pinned={ this.state.sidebarPinned } width={ 5 }>

<IconButton icon='close' onClick={ this.toggleSidebar }/>

Supplemental content goes here.

                </Sidebar>
            </Layout>
        );
    }
}

return <LayoutTest />;

That dark icon menu in the pinned NavDrawer has its menu cropped by the drawer.

Tried the overlay fix as recommended here, but with no success: https://github.com/react-toolbox/react-toolbox/issues/683
I tried applying it to all the ancestors from NavDrawer till the root Layout, and even to the children till Menu.

I'm sorry, it worked.

repo: react-toolbox/react-toolbox


text:
Fixed issue of scrollbar being hidden on Autocomplete and Dropdown components

Dropdown and Autocomplete components had a width: 0 and height: 0 css rules. These don't serve any purpose and make users not know it's scrollable/there is more content, hence is bad user experience.
This fix takes out the two css lines to show scrollbar whenever necessary.

Hello @paddotk! Thank you for your contribution!
There are some conflicts with the css files, since we've renamed them to .module.css, could you solve those conflicts please?

@rubenmoya Pushed an update. I got many merge conflicts, but not with the css files though.
I solved every conflict as the version from origin/master and renamed the two css files to ~.module.css, I hope I did it right? I normally don't work with Github branches nor forks, so please forgive my ignorance, if any #maximumNoobage

Done

authors: paddotk rubenmoya


text:
Revert input error color

PR #379 (unintentionally, I assume) changed the default error color for inputs to yellow:

Oh shoot. I'm so sorry about that. I modified it for testing the required color and forgot to switch it back.

No worries, it's an easy fix. Thanks for the required hint patch, by the way!

@csmcanarney No problem. I'm glad I was able to contribute to this project.
@javivelasco FYI please merge this when you get time! Also can you let me know when the docs on the live site are going to be updated?

Hey guys! Thanks for the comments and PR. I'm spending some hours today updating dependencies and getting some stuff reviewed and done. If everything goes right I'm releasing a new version and pushing the docs not later than tomorrow

authors: KerenChandran csmcanarney javivelasco


text:
[BUG][Regression] Marshalling error

Describe the bug

"The application called an interface that was marshalled for a different thread." for the UWP head.
Working fine with wasm. Haven't tested other heads.
Steps To Reproduce

Throw within a ReactiveCommand action. Subscribe to ThrownException with an action with UI impact. It throws.
Here is a Repro based on Uno "Hello World".
Note: there are multiple commits:

Initial commit which repro the bug with version 16.3.5
others commits where I test with different version. 15.1.1 works, 16.1.1 fails

Expected behaviour

I've written this kind of code for years. It should not throw.
Screenshots

Environment

OS:        UWP
ReactiveUI Version:    16.3.5

Additional context

Might be worth trying adding "ReactiveUI.UWP" to the UWP project. We had to separate that to a different package for WinUI3 support. Let me know if there are any issues still.

@glennawatson
I don't think this issue is related with not having that package. Even with the latest version of ReactiveUI.Uwp I can reproduce the issue. I also ran into it as well while trying to update to the latest ReactiveUI versions on personal projects.
I narrowed down the code Francois provided to the minimum UWP example (Added the package you mentioned in it), and can still repro this. Should be easier to find out whats wrong:
https://github.com/AlexisPollonni/ReproBugThreadError/tree/uwp-repro-minimal-16.3.9
This is the message the exception gives when the button is pressed:
The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD))
And here's the stack-trace : (not that useful i know lol)
   at ReproThreadError.MainPageViewModel.<>c.<<-ctor>b__7_1>d.MoveNext()
It does indeed seem like its something related with the ReactiveCommand implementation.
Hope this is a simple fix, because this prevents any UWP apps from upgrading to newer versions :)

Fixed by #2999

Hi, I have just updated ReactiveUI from 15.1.1 to 16.3.10, and this problem is popping up for me.
I have created a very minimal repo to demo the problem I am having.
The line await Task.Delay(1000).ConfigureAwait(false); to try to force the result to return on a different thread.
Adding a breakpoint to Label.Text = val, When I ran this, it was on thread 14. From experience, I expect RxApp.MainThreadScheduler to force this onto thread 3.
Do I misunderstand what .ObserveOn(RxApp.MainThreadScheduler) is supposed to be doing?
This is acting as I expect it to up to version 15.1.1
System.Exception: 'The application called an interface that was marshalled for a different thread. (Exception from HRESULT: 0x8001010E (RPC_E_WRONG_THREAD))'

Feel free to open new issues, old issues are hard to track. Thanks

authors: AlexisPollonni FrancoisM Thorocaine glennawatson

repo: reactiveui/ReactiveUI


text:
WeakEventManager's WeakEventList isn't thread safe

Occasionally, I get a "System.InvalidOperationExceptionCollection was modified; enumeration operation may not execute." while iterating handlers in DeliverEvent (WeakEventManager line 340ish).  I'm not exactly sure why many people don't have this issue too but suspect it's because my ViewModel is getting it's properties set from ANT and BTLE hardware rather than a UI event.
I'm happy to submit a pull request; however, I'm not sure if it would be better to lock whenever changing or iterating handlers or if for performance it would be better to iterate on a copy collection.

This is most likely by design.

WeakEventManager was designed for use on a single thread so this is by design.

@jlaanstra, is it expected that all events a ViewModel interacts with will come through the UI thread?  This seems very limiting. Maybe, I'm misunderstanding the expected use. Can you help me out with a little more explanation?
It appears WeakEventManager is used for marshaling all property and collection changing and changed events on view-models.  Based on what you're telling me, this means that view-model properties and collections can only be changed from a single thread.  This puts me in a position where code in my view-model needs to care about the ui thread when being used with a view that has such a thing.  This is a violation of the encapsulation of the view.
Perhaps, the design is incorrect. This is a very easy problem to fix, I've made the fix in a version of my app that over 5k people have been using for a month or so now.  The exception went from happening several times a day to never happening. As I said before, I'll be happy to submit a patch or pull request if it helps.

I'm not sure if this is the same use case, but I am able to receive events in my ViewModels from separate threads.  The key is to use ObserveOn in order to marshal it correctly.
Ex.
var locationChangeObs =
  Observable.Publish<Location>(
    Observable.FromEventPattern<EventHandler<LocationChangedEventArgs>,LocationChangedEventArgs>(h => x.LocationChanged += h, h => x.LocationChanged -= h)
    .ObserveOn(RxApp.MainThreadScheduler));

@pdoh00, I'm aware that I can use the ObserveOn but it seems wrong to need to use the MainThreadScheduler in a ViewModel.  Only the view cares about the main thread, forcing this on the view model seems that it creates unnecessary burden that the developer has to be concerned with.  Isn't it more natural for the view to use ObserveOn(RxApp.MainThreadScheduler) and to have the bindings for views that need things to happen on the main thread to marshal to the main thread?
Come to think of it, I've noticed a time or two where a binding in Xamarin.iOS doesn't go to the main thread as I would expect it to and I have to fall back to using ObserveOn(RxApp.MainThreadScheduler) in the view model.  So, maybe this was a bigger design choice than just the WeakEventManager.
PS, didn't we have lunch a couple months back?

@lorentzm I don't want to be pedantic, but maybe some clarification on "is it expected that all events a ViewModel interacts with will come through the UI thread? ".  The answer to that is no.
But all notifications of change to a property updated from another thread will happen on that other thread.
The ViewModel is on the same thread as the View. If the view is bound to said property, it's going to get a notification on the wrong thread.  That's where the ObserveOn in the VM comes in.  By placing that on the event Subscription then the notifications end up getting marshaled back to the UI thread so the view works correctly :sparkles:
From the View(i.e. Code Behind) the syntax doesn't really support ObserveOn. this.Bind(...), this.OneWayBind(...).  In addition (after a discussion with @paulcbetts) it could cause some very difficult debug problems to add the ObserveOn inside the Bind.
As for the iOS expectation....I am not sure I would expect that the binding would go to the UI thread.  As per above RxUI won't marshal it.  I think it will be platform dependent at best.
In WPF for example scalars end up getting marshaled, but collections do not. If I use xaml binding.
PS. Yep we did have lunch a few months back. Thanks again

@pdoh00 Thanks for the explanation.  If there's a problem having the bindings enforce execution on the main thread then there's no reason to have the WeakEventManager safe for multiple threads.
Also, not so bad to use the ObserveOn in the view model now that I think about it. Less to worry about in the view so better reuse across platforms.

authors: jlaanstra lorentzm pdoh00


text:
Update Readme?

Maybe it's good to update the readme with the following:

Is this component ready to use or still a bit WIP? (10k downloads on npm last month)
Which branch should be used to target PR's to

Keep up the good work btw, the component works great! 🎉

The README is definitely in need of some love, as it is quite conservative in its wording. I personally use Autocomplete for a range of production applications without any problems. That being said, we still have a lot of work ahead of us.
master

Check. Thanks

The readme has seen a lot of love lately. AFAIK this issue is no longer applicable. Just reopen if I'm wrong!

authors: CMTegner tiemevanveen

repo: reactjs/react-autocomplete


text:
question

I am wonder why do you  use 'clicking prevention' technique like below:
https://github.com/reactjs/react-modal/blob/f715a69e31b00eaf7912595a9bd2d22ab5cecdb3/src/components/ModalPortal.js#L269
Why just not use e.stopPropagation() is that case?

Hi @wwwebman, you can check if you can get this in the logic of clicking and dragging from content > overlay and overlay > content. It would be great to find a cleaner way to do it.

I'll close this issue for clean up. Please reopen if you can discuss further on how we can archive this.
Thanks, @wwwebman.

ok, @diasbruno, thanks

authors: diasbruno wwwebman

repo: reactjs/react-modal


text:
[chore] added test for default parentSelector.

Acceptance Checklist:

[x] All commits have been squashed to one.
[x] The commit message follows the guidelines in CONTRIBUTING.md.
[x] Documentation (README.md) and examples have been updated as needed.
[x] If this is a code change, a spec testing the functionality has been added.
[x] If the commit message has [changed] or [removed], there is an upgrade path above.

Coverage remained the same at 86.721% when pulling 242f8039240ff1e6f7b4155dd8739ec11d29df88 on diasbruno:chore/added-test-for-default-parent-selector into f47e79db83ef6e855195447640005e1b796aaec4 on reactjs:master.

authors: coveralls diasbruno


text:
push broken - just adds a '#' to the url

I recently updated my packages, moving
    "react": "^0.14.3",
    "react-dom": "^0.14.2",
    "react-redux": "^4.0.0",
    "react-router": "^1.0.3",
    "redux": "^3.0.4",
    "redux-simple-router": "^1.0.2",
    "redux-thunk": "^0.1.0",

to
    "react": "^15.1.0",
    "react-dom": "^15.1.0",
    "react-redux": "^4.4.5",
    "react-router": "^2.4.1",
    "react-router-redux": "^4.0.4",
    "redux": "^3.5.2",
    "redux-thunk": "^2.1.0",

and now updating the url via push doesn't work. Instead, it just adds a hashtag to the url.
Any ideas what may be wrong?

Sorry - missed the piece in the docs about the routerMiddleware!

repo: reactjs/react-router-redux


text:
syncHistoryWithStore is removing (or ignoring) parseQueryString from history object

i've got some code that does this:
const memoryHistory = useRouterHistory(createMemoryHistory)({ parseQueryString, stringifyQuery})
memoryHistory.push(req.originalUrl)
const reduxStore = configureStore(memoryHistory)
const history = syncHistoryWithStore(memoryHistory, reduxStore)

when this code is called on a server render with params that aren't handled correctly out of the box (ie, /foo?a[]=1) my location object ends up with incorrect query params:
query: { 'a[]': 1 }

and these values are also stored in my routing store.
if i skip the syncHistoryWithStore call and set const history = memoryHistory my code works as expected and the location object's query object is set correctly (but not in my routing store)
query: {a: [1] }

i've looked over the syncHistoryWithStore code and i can't see anything off the top of my head that could be contributing to this but i've definitely narrowed it down. have you seen anything like this before?

actually i think the issue is here:
https://github.com/reactjs/react-router-redux/blob/master/src/sync.js#L103
this is overriding any previously set listen method and that's how useQueries works:
https://github.com/ReactTraining/history/blob/v2.x/modules/useQueries.js#L97

nevermind, this looks like user error. sorry for the noise.


text:
AppRegistry: Undocumented magical lazy loading causes exceptions - Invariant Violation: Module AppRegistry is not a registered callabel module (calling runApplication)

Hi
What is problem?
RN has Message Queue which tries to dynamically dispatch a message AppRegistry::runApplication. In my case Message Queue did not have key "AppRegistry" associated with object AppRegistry. App threw exception Invariant Violation: Module AppRegistry is not a registered callabel module (calling runApplication).
Why it happened?
After You import AppRegistry You have to call any method,
import { Text, AppRegistry } from 'react-native';

const App = (props) => (
  <View>
    <Text>App1</Text>
  </View>
);

AppRegistry.registerComponent('Appname', () => App);

because it has getter which lazy loads real app registry module
 get AppRegistry(): AppRegistry {
    return require('./Libraries/ReactNative/AppRegistry');
  },

and this module is added to to MessageQueue
BatchedBridge.registerCallableModule('AppRegistry', AppRegistry);

Why I had this problem?
I inherited some codebase with async registration of components, which did not made AppRegistry to be added to MessageQueue sooner than event AppRegistry::runApplication fired .
How would I fix this?

I can't edit Your docs, so I can only hint: I would add to documentation that it is required to trigger loading of app registry and that it is
I would probably add it to https://reactnative.dev/docs/appregistry , but there seems to be no Hello World code which is not aimed at Expo so I would create a Hello World page for it (You can have Hello World by running react-native init, but it is not explained)
Or better, I would stop magically lazy loading stuff and ideally introduced init methods

Thanks

I am sorry, wrong repo :/


text:
Add 'visual components' use case for forwarding refs

After a discussion on Twitter about the forwarding refs docs being an advanced use case, I was suggested to PR another use case which may happen quite frequently when using "visual components" (like a FancyButton that uses a button element) but you may still need a ref to the native element.
This is my first contribution to the docs and English is not my first language so please all suggestions are welcome!

This is great. I'm going to edit it a bit and take it in. Thanks.

Thanks for putting up a PR @duailibe! This looks like a nice improvement!

OK, I pushed a more comprehensive rewrite. I used this example as the base, expanded the explanation around it to really hammer how this feature works, and changed the blog post and the API reference to focus on the simple example. We still have the complex one on the page later, and we have a section both in HOC and in context docs with the complex one.

Blog post section: https://deploy-preview-798--reactjs.netlify.com/blog/2018/03/29/react-v-16-3.html#forwardref-api
Reference: https://deploy-preview-798--reactjs.netlify.com/docs/react-api.html#reactforwardref
Full doc: https://deploy-preview-798--reactjs.netlify.com/docs/forwarding-refs.html

authors: bvaughn duailibe gaearon


text:
🛑 Bellshade Website is down

In 0ca6a0a, Bellshade Website (https://bellshade.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Bellshade Website is back up in 55a66ab after 32 minutes.


text:
Auto-detect server IP for Android emulator

Related to #192.

Wonderful.  Thank you again!

repo: reactotron/reactotron


text:
Add execution order test

This test currently has a different execution order in my adapter, so let's document the expected execution order.

@SimonFrings Done. 👍

@kelunik thanks for the update 👍
The test itself in its functionality and the overall design looks great. I talked with @clue about this and it looks like your testcase is already covered by other tests and didn't raise the overall code coverage.
I would argue that it wouldn't make sense to add a test just to show a specific example of what is possible.

authors: SimonFrings kelunik

repo: reactphp/async


text:
clean out all the puts statements showing up on server

From @catmando on January 12, 2016 21:40
there are some puts statements or some kind of logging like this:
************************** React Server Context Initialized Components::Sessions::New *********************************************
showing up on the server
Copied from original issue: zetachang/react.rb#116

From @ajjahn on January 12, 2016 21:47
@catmando Removed the client side puts statements as well. We definitely don't want those in production. It would be nice to implement a proper logger that will obey log levels per environment.

repo: reactrb/reactrb


text:
Unable to get Recommonmark to Work

Background
I'm trying to enable users to write documentation in the more common Markdown format, rather than forcing them to learn reStructured Text.  As such, I'd like to use something such as recommonmark to enable this.
The AutoStructify documentation says that "AutoStructify makes it possible to write your documentation in Markdown, and automatically convert this into rST at build time".  I'm trying to do this at build time, but this doesn't appear to be happening.
Configuration
My configuration is based on the recommended configuration at https://github.com/rtfd/recommonmark/blob/master/docs/conf.py  (linked to from https://recommonmark.readthedocs.io/en/latest/index.html#autostructify):
# At top on conf.py (with other import statements)
import recommonmark
from recommonmark.transform import AutoStructify

project = 'LiteX SoC Project'
copyright = '2019, Anonymous'
author = 'Anonymous'
extensions = [
    'sphinxcontrib.wavedrom',
    "recommonmark",
]
templates_path = ['_templates']
exclude_patterns = []
offline_skin_js_path = "https://wavedrom.com/skins/default.js"
offline_wavedrom_js_path = "https://wavedrom.com/WaveDrom.js"
html_theme = 'alabaster'
html_static_path = ['_static']

source_suffix = {
    '.rst': 'restructuredtext',
    '.txt': 'markdown',
    '.md': 'markdown',
}

# At the bottom of conf.py
def setup(app):
    app.add_config_value('recommonmark_config', {
        'url_resolver': lambda url: github_doc_root + url,
        'auto_toc_tree_section': 'Contents',
        'enable_eval_rst': True,
        'enable_auto_doc_ref': True,
    }, True)
    app.add_transform(AutoStructify)

Then in my documentation tree I have the following in a file called usb.rst:
How to Use
----------

.. include:: D:\Code\Fomu\foboot\hw\deps\valentyusb\valentyusb\usbcore\cpu\howto.md

Issue
This doesn't cause howto.md to be rendered as Markdown, despite the fact that .md files are supposed to be rendered as Markdown.  Instead it gets included verbatim, without getting converted at build-time.

You need to have the *.md file or a symlink to it (see here) in the same folder as your conf.py.
When that is done include it in your toctree as you would a *.rst file (howto).

My mistake.  I seem to have misunderstood how recommonmark works.
My initial assumption was that it maps filename endings to text processors, and by providing an include directive that would let me mix markdown and reStructured Text in one file.
It appears as though this isn't how it works, and normally you can't mix formats within a single document.
I've since switched to use m2r which does allow for this.

authors: s-weigand xobs

repo: readthedocs/recommonmark


text:
Added ability to offer a buffer range to a publication

I wanted the ability to offer multiple buffers and combine them into a single message. I noticed a similar issue had been brought up recently #(394), so I figured I would share what I've done. Comments are welcome.

I had some time today to review how this is implemented in Java and modified the C++ version to map more closely to it.
Another thing I would like some feedback on is that some of the functions could be improved by removing the end iterator as a parameter. Since the length is calculated in the offer function, all the remaining calculations could be based off the length. Would it be beneficial to remove the checks against the end iterator? (Leaving it in will only catch scenarios where the iterator is improperly implemented or where one of the buffers is modified concurrently while being offered.)

There were quite a few conflicts, so I had to rebase. Let me know if there's anything else I need to do to get this pushed through.

Sorry for the delay. I'll look at this tomorrow for a full review. To be honest, not sure I like following the C++ algorithms technique of iterator template params. Not sure it fits here. But I'll review with an open mind. A std::array version feels closer.

No worries on the delay.
My main reason for wanting to use an iterator is because I have a use case involving a linked list of buffers and would prefer to not have to allocate an array on each offer. I figured that an iterator-based approach could cover both the linked list and array use cases. Unfortunately, this is a very C++-specific solution, so the code doesn't match exactly with the Java side of things. But I still tried to make it match up the best that I could.
If you have any questions or comments, or if you want any examples for unit tests or something, let me know. Thanks.

@nicklauslittle thanks! I spent some time exploring this and it does fairly well. It's a more C++-ishy way than using a native array. And probably better overall. Leaving options for usage with the standard algorithms is quite handy. Nice work!

Glad I could help out!

authors: nicklauslittle tmontgomery

repo: real-logic/aeron


text:
truncateRecording doesn't effectively deletes the recording

Hi!
I've added a test which shows what exactly doesn't work. The second checkRecordingsCount fails.
Did I right understand

Truncating a recording to the start position effectively deletes the recording.

? My understanding It should remove a recording at all but now it leaves a record with startPosition=0 and endPosition=0.
(BTW is an issue report like this OK? )

@mjpt777 can confirm, but I believe the desired effect is to delete all the segment files. This then allows ClusterTool to mark the entry as INVALID when run with verify.

The behaviour is as expected. After a full truncate back to startPosition there are no segment files and the entry in the catalog reflects this. This commit show clarifies the state after a full truncate. https://github.com/real-logic/aeron/commit/0c0d0b54178521246d8c6208e0639d2eb5b40c6e

@QIvan This is a reasonable way to raise an issue. A refinement would be to raise an issue and reference a PR. In the PR it is good to @Ignore the test so CI can pass the PR.

@mjpt777 Ok got. The good point about @Ignore thanks.

if we have 2 records:
0 -> [0 ... 100]
1 -> [0 ... 200]

then we truncate recording 1 to the 0 position. Now we have
0 -> [0 ... 100]
1 -> [0 ... 0]

Right?
Is it possible somehow to completely remove  a recording then?

The catalog retains the entry because the recording id should not be reused.

authors: QIvan mjpt777 tmontgomery


text:
[Java] sbe 1.16.3 generates noisy Java code

Please cleanup the SBE generated Java code. Here is SBE-generated snippet of code:
public SetFileAttributesEncoder putPath(final DirectBuffer src, final int srcOffset, final int length)
    {
        if (length > 1073741824)
        {
            throw new IllegalStateException("length > maxValue for type: " + length);
        }

        final int headerLength = 4;
        final int limit = parentMessage.limit();
        parentMessage.limit(limit + headerLength + length);
        buffer.putInt(limit, (int)length, java.nio.ByteOrder.LITTLE_ENDIAN);
        buffer.putBytes(limit + headerLength, src, srcOffset, length);

        return this;
    }

To which the Java compiler says:
..../hasql/message/src/main/java/dynamind/hasql/message/SetFileAttributesEncoder.java:215: warning: [cast] redundant cast to int
        buffer.putInt(limit, (int)length, java.nio.ByteOrder.LITTLE_ENDIAN);

This is very irritating because it is outside the developer's control, pollutes reports and CI builds.

We welcome contributions and sponsorship.

Thanks @mjpt777 , I was gonna pick this change up, but I see you did it already!
Here is the compiler switches I used to generate the warnings:
subprojects {
    apply plugin: 'java'
    sourceCompatibility = JavaVersion.VERSION_14
    targetCompatibility = JavaVersion.VERSION_14
    tasks.withType(JavaCompile) {
        options.incremental = true
        options.encoding = 'UTF-8'
        sourceCompatibility = JavaVersion.VERSION_14
        targetCompatibility = JavaVersion.VERSION_14
        options.compilerArgs  << "-Xlint"<<"-Xlint:-try"
    }
}

Also, while at that pls upgrade Gradle to 6.3

Gradle 6.3 is just released. We will upgrade in time. We only take direct action for customers who provide us with commercial support.

That is fine, but Java 14 requires Gradle 6.3

repo: real-logic/simple-binary-encoding


text:
Realm.Configuration is not listed on a sidebar in RealmSwift API Reference

https://realm.io/docs/swift/latest/api/Classes.html
The only link I've found is Realm class page -> configuration property.

Jazzy issue: https://github.com/realm/jazzy/issues/64

Fixed in realm/jazzy#567

authors: jpsim stel

repo: realm/realm-cocoa


text:
ProgressNotification callback not triggered without receiving data from sync in Realm 10

Goals
Listening ProgressNotification to see if there is pending data to download.
Expected Results
The ProgressNotification callback for download to be triggered without an initial download.
Actual Results
The ProgressNotification callback for download is not triggered until new data are received.
From this point, It will trigger every time we need it, even if no data are received
Steps for others to Reproduce
We are using MongoDB Realm in our app.
The first time the user is connected to the app, the ProgressNotifcation callback is triggered correctly, and it will work and trigger whenever a new download is coming.
Even if no download is pending, the ProgressNotification callback will be triggered (the Progress object pass in the callback will contain values from the last download) at least once(when creating it). I supposed this is due to the fact that we are downloading the first data set of the user.
But after killing the app and launching it again, the ProgressNotification callback is not triggered anymore until new data are received by the app. And from this point, the callback will be called every time we need it.
It seems that now, the framework needs a first download since the app is launch to make ProgressNotification callback to be triggered every time we need it.
This was working in the previous version of Realm (5.X.X). We just finished the migration to Realm 10 and discover this issue.
Is something has changed? Is this working as intended according to you?
Note: this is no more working in both mode : .forCurrentlyOutstandingWork and .reportIndefinitely
Code Sample
self.token = syncSession.addProgressNotification(for: .download, mode: .forCurrentlyOutstandingWork) { progress in
                           .......Some code........   <- this part of the code is not triggered anymore
}

Version of Realm and Tooling
Realm framework version:  10.5.0
Realm Object Server version: MongoDB Realm
Xcode version: 12.3
iOS/OSX version: 14.3
Dependency manager + version: Cocoapods 1.10.0

@fealebenpae do you have any thoughts on this?

Hello ! I am still stuck on this issue. Is there any news from your side?
Thanks

Hello ! I am still stuck on this issue. Is there any news from your side?
Thanks

Hi @erdem-inan,
Sorry for the delay. I will check back with @fealebenpae.
Kind regards,
Dominic

Hi @erdem-inan,
Sorry for the delay. I will check back with @fealebenpae.
Kind regards,
Dominic

@erdem-inan Trying to clarify this further for us so that we can reproduce it:
I suppose the problem is that progress notifications are delivered only if this is the first time the realm file is opened and synchronised from the server?
@simonask  Do you think we have enough information to reproduce this issue?

@erdem-inan Trying to clarify this further for us so that we can reproduce it:
I suppose the problem is that progress notifications are delivered only if this is the first time the realm file is opened and synchronised from the server?
@simonask  Do you think we have enough information to reproduce this issue?

Hi @DominicFrei !
Yes, it is that.
So, at first lunch, it is working great and as expected (since we have data to download).
But after, let say that we kill the app and restart it. The progress notifications will no more deliver notifications until new data is pushed to the Realm (through MongoDB with the right Partition key).

Hi @DominicFrei !
Yes, it is that.
So, at first lunch, it is working great and as expected (since we have data to download).
But after, let say that we kill the app and restart it. The progress notifications will no more deliver notifications until new data is pushed to the Realm (through MongoDB with the right Partition key).

Hello @DominicFrei ! Any news on this issue?

Hello @DominicFrei ! Any news on this issue?

@erdem-inan The issue has been passed on to @leemaguire. He is looking into similar issues already.

@erdem-inan The issue has been passed on to @leemaguire. He is looking into similar issues already.

This is confirmed as fixed with the latest version of Cocoa.

authors: DominicFrei erdem-inan jsflax leemaguire