Add convenient methods for DeepLinkReceived event (close #474)

I've added a couple of factory methods to generate a DeepLinkReceived event from an Intent or a ReferrerDetails.
The Intent is provided by the Activity that receives the deep link. The developer can create the DeepLinkReceived event just passing the Intent.
Same for the ReferrerDetails. In this case the ReferrerDetails is generated by the Install Referrer Library that can be added as a dependency by the developer. We don't force this dependency and it's optional in the tracker.
Below the suggested documentation (that integrate the one in PR: https://github.com/snowplow/snowplow-android-tracker/pull/472)

Deep Linking
In the mobile world the Deep Links are url that links to a specific content directly in a mobile app. Usually they are used to redirect the user from a website or a banner-ad to the installed app instead of another web page. The Deep Links help the user to go straight to the content they are interested of inside the app, similarly to the navigation in the web.
Usually the Deep Link is received by the mobile operating system and passed to the related app. It's the responsability of the developer to parse the received deep-link's url and show the right content to the user. The way the Deep Link is used is strongly dependant by the way the app routing is implemented. For this reason, our mobile tracker can't automatically track the Deep Link, but we provide an out-of-the-box event that can be used by the developer to manually track it as soon as the Deep Link is received in the app. It will be duty of the tracker to automatically attach the informations of the Deep Link to the first ScreenView tracked.
The Android platform documentation provides clear instructions about how to declare the Deep Links that the app is able to handle. Following those instructions, to enable Deep Link support in your app you should declare an intent filter in your AndroidManifest.xml that sends the Deep Link to the selected Activity as an intent.
In practice, when the activity receives the Intent, the developer can track it through the DeepLinkReceived event.
For example (in your Activity):
@Override
public void onCreate(Bundle savedInstanceState) {
    ...

    // Extract info from Intent
    Intent intent = getIntent();
    String deepLinkUrl = intent.getData().toString();
    String referrer = null;
    Bundle extras = intent.getExtras();
    if (extras != null) {
        Uri referrerUri = extras.get(Intent.EXTRA_REFERRER);
        if (referrerUri != null) {
            referrer = referrerUri.toString();
        }
    }
    // Create and track the event
    DeepLinkReceived event = new DeepLinkReceived(deepLinkUrl).referrer(referrer);
    tracker.track(event);

    ...
}

It's also possible to use the factory method fromIntent that directly generates the DeepLinkReceived event from an Intent passed.
@Override
public void onCreate(Bundle savedInstanceState) {
    ...

    // Generate event directly from an Intent
    Intent intent = getIntent();
    DeepLinkReceived event = DeepLinkReceived.fromIntent(intent);
    // Create and track the event
    if (event != null) {
         tracker.track(event);
    }

    ...
}

The deep link can be received by an already installed app. In case the developer wants to receive a deep link of a fresh installed app, they have to use the Install Referrer Library which can provide the original deep link url.
The Install Referrer Library is an Android standard library that can be instrumented as explained here. The Snowplow Android tracker doesn't force this dependency so the developer has to add the dependency on gradle:
dependencies {
    ...
    implementation("com.android.installreferrer:installreferrer:2.2")
}

The ReferrerDetails will be accessible as explained here. In there you can generate the DeepLinkReceived event and track it.
@Override
    public void onInstallReferrerSetupFinished(int responseCode) {
        switch (responseCode) {
            case InstallReferrerClient.InstallReferrerResponse.OK:
                ...
                // Generate event directly from an ReferrerDetails
                ReferrerDetails referrerDetails = referrerClient.getInstallReferrer();
                DeepLinkReceived event = DeepLinkReceived.fromReferrerDetails(referrerDetails);
                // Create and track the event
                if (event != null) {
                    tracker.track(event);
                }
                ...

Every time a DeepLinkReceived event is tracked, the tracker keeps memory of the tracked Deep Link url and will attach a Deep Link entity to the first ScreenView tracked in the tracker.
This is helpful during the analysis of the data because it will be clear the relation between the content visualized by the user (ScreenView event) and source (DeepLink entity) that originated that visualization.
This behaviour is enabled by default but it can be disabled from the TrackerConfiguration.
For example:
TrackerConfiguration config = new TrackerConfiguration()
    ...
    .deepLinkContext(false)
    ...

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

A similar issue about the topic (noticed now): https://github.com/snowplow/snowplow-android-tracker/issues/249


recent projects

it is already stored in meta.history
TODOs:

insert to array, maybe add timestamp, allow only size of 10 projects
show only filename, basename in tooltip

remove duplicates from history


{CI} Revert to use azdev release version

Description
Fix https://github.com/Azure/azure-cli/issues/14301
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change.
[Component Name 2] az command b: Add some customer-facing feature.

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

add to S172

The version of azdev in our CI is not consistent. Should we remove install_azdev.sh at all and refine the installation script for azdev?
Meanwhile, the latest released azdev should have wrong dependency. We should release the new version of azdev ASAP.

Please help https://github.com/Azure/azure-cli-dev-tools/pull/227


Rank tests

contains t-test and bootstrapping correction stuff already, merge after those.
This implements rank tests for evaluation Tensors. Will also implement these into model plots.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8

Complexity increasing per file
==============================
- pyrsa/inference/crossvalsets.py  2
- pyrsa/inference/evaluate.py  3
- pyrsa/vis/model_plot.py  10

Clones added
============
- pyrsa/inference/evaluate.py  1
- pyrsa/util/inference_util.py  2

Clones removed
==============
+ tests/test_crossval.py  -5
+ tests/test_inference.py  -6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8

Complexity increasing per file
==============================
- pyrsa/inference/evaluate.py  3
- pyrsa/inference/crossvalsets.py  2
- pyrsa/vis/model_plot.py  4

Clones added
============
- pyrsa/inference/evaluate.py  1
- pyrsa/util/inference_util.py  2

Clones removed
==============
+ tests/test_inference.py  -6
+ tests/test_crossval.py  -5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8

Complexity increasing per file
==============================
- pyrsa/inference/crossvalsets.py  2
- pyrsa/vis/model_plot.py  4
- pyrsa/inference/evaluate.py  3

Clones added
============
- pyrsa/util/inference_util.py  2
- pyrsa/inference/evaluate.py  1

Clones removed
==============
+ tests/test_crossval.py  -5
+ tests/test_inference.py  -6

See the complete overview on Codacy

Codecov Report

Merging #145 into master will increase coverage by 5.46%.
The diff coverage is 65.53%.

@@            Coverage Diff             @@
##           master     #145      +/-   ##
==========================================
+ Coverage   75.63%   81.09%   +5.46%
==========================================
  Files          57       50       -7
  Lines        5335     4866     -469
==========================================
- Hits         4035     3946      -89
+ Misses       1300      920     -380

Impacted Files
Coverage Δ

pyrsa/vis/model_plot.py
4.24% <3.92%> (+0.38%)
:arrow_up:

pyrsa/util/inference_util.py
69.69% <65.67%> (+1.83%)
:arrow_up:

pyrsa/inference/crossvalsets.py
89.62% <69.23%> (-1.58%)
:arrow_down:

pyrsa/inference/result.py
82.19% <82.35%> (-0.57%)
:arrow_down:

pyrsa/inference/evaluate.py
88.63% <83.06%> (-8.26%)
:arrow_down:

pyrsa/inference/__init__.py
100.00% <100.00%> (ø)

pyrsa/inference/boot_testset.py
98.61% <100.00%> (ø)

pyrsa/inference/bootstrap.py
100.00% <100.00%> (ø)

tests/test_crossval.py
100.00% <100.00%> (ø)

tests/test_inference.py
100.00% <100.00%> (ø)

... and 9 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 316b984...94eb649. Read the comment docs.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8

Complexity increasing per file
==============================
- pyrsa/inference/crossvalsets.py  2
- pyrsa/inference/evaluate.py  3

Complexity decreasing per file
==============================
+ pyrsa/vis/model_plot.py  -16

Clones added
============
- pyrsa/vis/model_plot.py  2
- pyrsa/util/inference_util.py  2
- pyrsa/inference/evaluate.py  1

Clones removed
==============
+ tests/test_crossval.py  -5
+ tests/test_inference.py  -6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8

Complexity increasing per file
==============================
- pyrsa/inference/evaluate.py  3
- pyrsa/inference/crossvalsets.py  2

Complexity decreasing per file
==============================
+ pyrsa/vis/model_plot.py  -16

Clones added
============
- pyrsa/inference/evaluate.py  1
- pyrsa/vis/model_plot.py  2
- pyrsa/util/inference_util.py  2

Clones removed
==============
+ tests/test_inference.py  -6
+ tests/test_crossval.py  -5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 2

Complexity increasing per file
==============================
- pyrsa/inference/evaluate.py  3
- pyrsa/inference/crossvalsets.py  2
- tests/test_vis.py  1

Complexity decreasing per file
==============================
+ pyrsa/vis/model_plot.py  -16

Clones added
============
- pyrsa/inference/evaluate.py  1
- pyrsa/vis/model_plot.py  2
- pyrsa/util/inference_util.py  2

Clones removed
==============
+ tests/test_crossval.py  -5
+ tests/test_inference.py  -6

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8
- Added 2

Complexity increasing per file
==============================
- pyrsa/inference/evaluate.py  3
- pyrsa/inference/crossvalsets.py  2

Complexity decreasing per file
==============================
+ pyrsa/vis/model_plot.py  -16

Clones added
============
- pyrsa/vis/model_plot.py  2
- pyrsa/util/inference_util.py  2
- pyrsa/inference/evaluate.py  1

Clones removed
==============
+ tests/test_inference.py  -6
+ tests/test_crossval.py  -5

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 8

Complexity increasing per file
==============================
- pyrsa/inference/evaluate.py  3
- pyrsa/inference/crossvalsets.py  2

Complexity decreasing per file
==============================
+ pyrsa/vis/model_plot.py  -13

Clones added
============
- pyrsa/inference/evaluate.py  1
- pyrsa/vis/model_plot.py  2
- pyrsa/util/inference_util.py  2

Clones removed
==============
+ tests/test_inference.py  -6
+ tests/test_crossval.py  -5

See the complete overview on Codacy


Traceback: NameError: name 'conditional_dependencies' is not defined

Happens on openSUSE Tumbleweed:
Information for package python-py2pack:
---------------------------------------
Repository: openSUSE-20150516-0
Name: python-py2pack
Version: 0.4.10-3.1
[..]

py2pack generate jrnl -t opensuse.spec -f python-jrnl.spec
generating spec file for jrnl...
Traceback (most recent call last):
  File "/usr/bin/py2pack", line 22, in <module>
    main()
  File "/usr/lib/python2.7/site-packages/py2pack/__init__.py", line 255, in main
    args.func(args)
  File "/usr/lib/python2.7/site-packages/py2pack/__init__.py", line 155, in generate
    _augment_data_from_tarball(args, tarball_file[0], data)
  File "/usr/lib/python2.7/site-packages/py2pack/__init__.py", line 117, in _augment_data_from_tarball
    _parse_setup_py(f.extractfile(setup_filename), data)
  File "/usr/lib/python2.7/site-packages/py2pack/__init__.py", line 104, in _parse_setup_py
    data["install_requires"] = eval(match.group(1))
  File "<string>", line 7, in <module>
NameError: name 'conditional_dependencies' is not defined

This is almost certainly the same issue as #41; please take a look there and see if the proposed pull request #42 helps you understand what's going wrong.

Works for me with the latest commit (54e5358560363ee1377f972dcf9a704ffe2efadf). I'll update the openSUSE package as soon as a new release is on pypi.


Optimize code for revising insertStatement

Fixes #1844 .

Pull Request Test Coverage Report for Build 6796

13 of 21 (61.9%)  changed or added relevant lines in 4 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.03%) to 74.297%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

sharding-core/src/main/java/org/apache/shardingsphere/core/routing/type/standard/StandardRoutingEngine.java
0
8
0.0%

Files with Coverage Reduction
New Missed Lines
%

sharding-core/src/main/java/org/apache/shardingsphere/core/routing/type/standard/StandardRoutingEngine.java
1
65.52%

Totals

Change from base Build 6795:
0.03%

Covered Lines:
10652

Relevant Lines:
14337

💛  - Coveralls


Feat: Adding prop explorer for AirBnB rating

Is your feature request related to a problem? Please Describe.

The props explorer for (AirBnB) is missing.

Describe the solution you'd like

Introducing AirbnbRating.mdx.

Additional context

Please see the bottom right corner.(no options for viewing props.)

@pranshuchittora, I would like to work on the above-mentioned issue.  Already started working on it. Please assign me the task.
Thanks :)

I would also like to add another props explorers, is it fine?
**Attaching below the list, I will be working on: **

buttongroup.mdx
checbox.mdx
Header.mdx
icon.mdx
image.mdx

For now, I think this would be enough. Maybe, later I'll be adding more contributions.

This seems to be similar to https://github.com/react-native-elements/playground/issues/41

@pranshuchittora, I think the #41 is trying to add additional props and update the older ones, while I am trying to Document  in an markdown it.

The explorer is no available for many components.
@pranshuchittora,

Yeah, go ahead. Make sure there's no open PR

@Uyadav207 it's quite a big issue so please can u let me work on header.mdx

@nlok5923, Actually I have started working. but don't worry, please Go for.... pricing.mdx.
👍🏿

@pranshuchittora, can you assign me?
This will help to reduce the repetitive issues.

@nlok5923, Actually I have started working. but don't worry, please Go for.... pricing.mdx.
👍🏿

Thanks working on pricing.mdx

Yeah, go ahead. Make sure there's no open PR

Sure, working on it.

Expected
Total number of ratings to display

Type
Default

number
5

defaultRating

Initial value for the rating defaultRating

Type
Default

number
1

@pranshuchittora, How can I resolve this?
please help me out.

Expected
Total number of ratings to display
Type 	Default
number 	5
* `defaultRating`

Initial value for the rating defaultRating
Type 	Default
number 	1

@pranshuchittora, sir ... How to style MDX........ DO I need to make style modules for MDX styling..... as MDX follows JSX. ??


Kanban Board Review

https://github.com/jmonto55/javascript_api_based_webapp/projects/1
Hi Reviewer,  just as a quick note, we are 2 members in our team: @SFarida @jmonto55

Hi team,
✔ Status: APPROVED 🏆 🎉 🎊
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights

All tasks were assigned 👌

Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Can I start using the ES6 codebase?

Since ES6 has now been officially released, I guess its ok to start using it? Is ng-poly es6 code safe to use for my new commercial app/project?

ng-poly uses Babel, so ES6/2015 will be transpiled to ES5. It should be good to go in regards to that. If you find any bugs or have suggestions on how we can improve the setup please let us know.


Charles Proxy HAR converter script

The current HAR converter script outputs a format that Charles displays in a way the user doesn't expect, since it doesn't have a display option to show the DNS name instead of the IP address in the Host column. To work around it, I've modified the script to overwrite the response.url key with the value from the host header if present, and fall back to default behavior if not.
It's almost a line-for-line copy of the current har_dump.py with an additional function to make the switch.

Fixing the lint failures now.

Are we following the HAR spec, is Charles following the HAR spec, or is the HAR spec just too vague?
I think there'd be value in having interop by default. I'd be more in favor of changing the current har dump script than adding a second one which is mostly a copy.

I can look into this with http://www.softwareishard.com/blog/har-12-spec/. IMO, it's not really a problem with what data is put in the log.entries.request.url key, but rather how the program interprets it for the user. Putting in the IP address of the server as the URL isn't incorrect when that's how it gets requested, but Charles doesn't automatically adjust the display for users to swap in the DNS name like MITMWeb does.

Per HAR spec:
"url [string] - Absolute URL of the request (fragments are not included)."
So if the IP is the Absolute URL, then that seems correct to me.

Let this one simmer a bit - I've unearthed bugs in the output when loading into Charles, since it's very picky about the format.

Ok, got the formatting changed so Charles will take the HAR (it was expecting the URL field to container the http or https). Also let me know if my assumptions are correct - I'm assuming that a positive SSL timing value means https was used, and a 0 or negative means http.

Thanks for your work here - can you please integrate your changes in the existing har dumper (i.e. overwrite that one)? I don't think we need to scripts doing almost the same stuff. :)

Hi - we'd love to get this merged. Any update on this?

I think the current HAR script was just developed from the spec without compatibility with any particular application in mind. I'd be perfectly fine with adjusting our current HAR dumper entirely to what Charles does/supports. :)


DSA <IP_ADDRESS> Strings : Palindrome Problems (Problem-4)

Description
Description
Longest Palindromic substring
Task

[ ] Audio
[ ] Video
[ ] Documentation

Note

While requesting the issue to be assigned, please mention your NAME & BATCH NUMBER.
Mention the type of contribution you want to make.
Kindly refer to the Issue Guidelines.
Do not use the assign command for this issue. Follow the above procedure.
In case you see that the issue has already been assigned, try to request a different task within the same issue.
Changes should be made inside the DSA/directory & DSA branch.
Name of the file should be the same as the issue.
This issue is only for 'GWOC' contributors of the 'DSA' Domain.

Domain
DSA
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

Vanshika Sable Batch 1 type- documenatation

/assign

@goelesha mam please assign me this issue .

@aishapervin It has been mentioned to not use assign command in the issues created by the supervisors. Refrain from doing this.
@VanshikaSable Assigning the issue to you. Make sure to submit a PR within 7 days
All the Best !!

@goelesha  mam i cant see strings folder in dsa branch . i can see only  arrays and algorithms folder. what should i do now.please help.

can you please share the link

Check out the DSA branch. There you will see all the 4 folders.

@goelesha review pr and tell any changes needed. thank you.


#pytorchlightning-version

Hi, Jusper. I came across the following issue when i used the code you provided. Maybe it's the pytorchlightning version problem, could you show me the requirements of your code?

pytorch-lightning           2.0.9.post0
torch                       1.13.1+cu116

I have the same requirements with you, could you give some suggestion to solve the issue i met with?

I've encountered similar errors in the past. It appears there's a RuntimeError in your DataLoader worker process. This can be caused by several reasons:

Make sure you have enough memory available, as DataLoader processes can be memory-intensive.
Ensure that your dataset returns items correctly and doesn't have any underlying issues that might cause a process to fail.
Try reducing the number of workers in the DataLoader, or set num_workers=0 to see if the problem persists.

If you could provide more details or share the exact error message the DataLoader is raising, it might help in pinpointing the problem more accurately.

Thank for your quick answer. I will try your advice and give my feedback.


Bug: on command region argument not working

The region argument (in < area > ) for on command doesn't seem to work.

Post script, and some explanation of why you think it doesn't work?

Still exists,
on myCommand command: <-- this runs
on myCommand command in 172: <-- this not
Maybe somewhere a minor typo in the event-parser ?

do you really have a cuboid named 172

Its the name of my world.

That's a horrible world name. Also, patch in latest dev

Fix confirmed.


Less formatting and includes

Is there anyway to format less files?  I have formatting working with HTML and Typescript files.
Is there any way to get the intellisense working with variables defined inside a less import similar to how you can add extra libs with Typescript.

For VSCode there are extensions that format LESS. For Monaco there is not and is also not planned.
Inetllisense across files for LESS: Again there is an extensions for VSCode (Less Intellisense), nothing planned for Monaco.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


[PE-D][Tester C] Edit flaw

You are able to edit fields for clients until they are all the same, even if this is prevented in the add feature
eg.

copy the add for index 1
change phone by 1 digit
edit the newly added client's phone to be the same as index 1

Labels: type.FeatureFlaw severity.Medium
original: Harithhh06/ped#4

Ignored again, for the same reason as we ignored the other issues from this tester. He has used<EMAIL_ADDRESS>and<EMAIL_ADDRESS>which count as two separate emails, thus they are not duplicates.


font weight selector

This is a proposed implementation for font weight selection that adds following features:

font weight setting for editor font
font weight selector for editor font

This closes #3161
This is how font weight selector looks like in settings:

And here is font weight change in action:

Test on my machine shows that if selected font weight does not exists then closest to it will be rendered.

Thanks for taking your time to review my pr, and providing useful suggestions
As suggested, i improved following things:

Converted EDITOR_FONT_WEITGHTS from array to object
Now all font changes handled in one handler
Added some screenshots/gif to the description

@develohpanda i was not yet able to find an elegant solution that will allow display only installed weights for each font. But i can give it another try this weekend maybe.

@develohpanda so i think i found a solution that works and also not very hard to understand.
now only installed weights are shown for selected font:

Great work @danilkhromov looks good.

@develohpanda i have a windows in the vm, so hopefully i will be able to reproduce this behavior there. Im also assuming that this is caused by the fontScanner, seems like it returns slightly different data on windows.
I will look into that on the weekend and also will take care of other things that you mentioned (sorry if there is some obvious mistakes, im mostly developing backend services and i dont have very deep knowledge of js and react).
Hopefully i will be able to tackle the windows issue, but if not, then your help will be much appreciated :slightly_smiling_face:

Open-source is a really great way to learn and practice, so no worries at all! and no rush, take your time 🤗

Code generally looks good to me, but while testing on Windows it doesn't seem to be working as intended.

I will be away for the next week or so, and can take a swing at Windows when I'm back, in case you don't have access to a Windows dev machine. Also, don't worry about keeping up to date with develop, I'll make sure it's up to date before merging. hugs Thank you for your patience!

after some investigation it looks like fontScanner on windows returns different data compared to what i have on linux (and i assume on macOS as well). family in the font object on windows contains full name of each installed variant e.g. JetBrains Mono Medium while on linux/macOS family contain only JetBrains Mono thus same way of collecting weights with findFontsSync does not work. Also for some reason findFontsSync always returns empty array on windows, even if i use some hardcoded values like Consolas or JetBrains Mono.
Not sure what would be the best approach in that case, getting all the weights for each font immediately might also result in different behavior on windows since it shows each installed font in separate family :disappointed:
Any suggestions how i can tackle this would be much appreciated.

Thanks for that investigation! We all just love the differences between operating systems 😝 I'll spend some time on Windows next week and get back to you!

Closed as stale.


Category label is not updated after adding one category

After adding a category, currently there is no any visual feedback that tells the user that the category is added.

Current workaround: refresh the whole page
Expected: UI should show that the category is added immediately (or shortly after API response)

I want to fix the issue.

Working on this.
I think this bug was introduced by cf550a0c.
Console shows this error:
Invariant Violation: Can't find field articleCategories on object {
  "id": "91m530brhhfo",
  "text": ...
  ...
  "articleCategories({\"statuses\":[\"NORMAL\"]})": [
    {
      "type": "id",
      "generated": false,
      "id": "ArticleCategory:91m530brhhfo__oT2o7nEBrIRcahlYKQoM",
      "typename": "ArticleCategory"
    }
  ],
  "stats": [
    ...
  ],
  "user": {
    ...
  }
}

readFragment() (called in components/ArticleCategories/CategoryOption.js) throws an error because the key of the categories array is articleCategories({"statuses":["NORMAL"]}) instead of the expected articleCategories.
To work around the problem, I suggest we always fetch all categories (remove statuses filter in query) and instead we change the display of categories according to whether the user is blocked and category status equals BLOCKED.

Eventually I found a simpler way to solve the problem; please have look at my PR :slightly_smiling_face:


New serialization format for log redo records.

This PR is a significant rewrite of how the log manager serializes the delta record in a RedoRecord.  It goes most of the way towards fixing #262.
The log manager now dives into the guts of a delta record to determine how to serialize it.  The three essential pieces of information that are always written out are: (1) the number of columns, (2) the projection list, and (3) the null bitmap.
The log manager then uses the null bitmap and block layout to determine whether/how to write out an attribute value.  If the column is null, then nothing is written out. Else, the log manager consults the BlockLayout to determine whether the column is inline or varlen. If inline, it writes out the delta's inline value; else, it follows the pointer to the varlen entry and writes out those contents.
As an example of how the log file can be processed on recovery, see the rewritten implementation of ReadNextRecord() within test/storage/log_test.cpp. We'll assume that the process responsible for recovery will have access to the BlockLayout through some other means (presumably with checkpoint / catalog).
As an initial proof of concept, I've tested this with the existing log tests (which do not have any varlen columns).  I also increased the number of rows in the test table to 10 (from 1), so that things are a little more robust. When we do "bookkeeping" with only 1 row, that means only 1 update ever actually gets written to the log file.  Adding tests for logging of varlen columns will be the next step.

I will improve coverage on the untested cases (null column, varlen column, Delete) in the next few days, but I think the main logic is all ready for review.

@songzhaozhe @codeworm96 @lmy1229 You guys are going to need to merge this PR into your code. It fixes storing VARCHAR values in log records.

Oh cool, glad someone is picking back up on this! Let me know if you have
questions about this PR.
On Wed, Apr 17, 2019 at 5:39 PM Andy Pavlo<EMAIL_ADDRESS>wrote:

@songzhaozhe https://github.com/songzhaozhe @codeworm96
https://github.com/codeworm96 @lmy1229 https://github.com/lmy1229 You
guys are going to need to merge this PR into your code. It fixes storing
VARCHAR values in log records.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cmu-db/terrier/pull/263#issuecomment-484312131, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFB7UIKNNH4WX6PC5H2VUMLPQ67KRANCNFSM4GIUAOUQ
.

How is the progress of tests (null column, varlen column, Delete)? Are you still working on it or we should take over?

@songzhaozhe Justin has graduated and is not working with us anymore. He has a new lover in California.

Since we do not have access to the original branch, shall we fork out a new branch and create another pull request, or directly merge this branch into our code (in this case the GC group will have to branch out from our code)?

The first step would be adding uncovered tests to ensure the details are correct.

Sorry for the delayed response -- Andy's right (though I wouldn't quite put
it in those terms).
Did you figure out what to do with branching/merging? If there's anything I
can do to change the permissions on that branch, I'm happy to do so.
Thank you for extending my work / adding test coverage!
On Thu, Apr 25, 2019 at 1:22 PM songzhaozhe<EMAIL_ADDRESS>wrote:

The first step would be adding uncovered tests to ensure the details are
correct.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/cmu-db/terrier/pull/263#issuecomment-486824047, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFB7UIMGOAWPQJQYYYT2IPLPSIHIHANCNFSM4GIUAOUQ
.

Hi Justin, yes we have merged your branch into our PR and are working on it. So probably no further action is needed on your side.

Incorporated into #370


Make S.Tree.t abstract

S.Tree.t was previously a concrete type with redundant constructurs of_node and of_contents. In some places, we were using these constructors; in others, we were constructing the value directly.
This change encourages delegation by requiring all instances of S.Tree.t to go via the constructors and destructors in S.Tree.
I made this change last week while experimenting with 'foreign' hashes support (which likely want to add a case to this type), but I think it stands as an improvement by itself.

Rebased :slightly_smiling_face:


Correction for raw affiliation Schulich School of Medicine and Dentistry (Richard, Glazer, Demirkaya, Karp), Western University

Correction needed for raw affiliation Schulich School of Medicine and Dentistry (Richard, Glazer, Demirkaya, Karp), Western University
raw_affiliation_name: Schulich School of Medicine and Dentistry (Richard, Glazer, Demirkaya, Karp), Western University
new_rors: 02grkyz14
previous_rors: 05cgtjz78
works_examples: W4366338441
contact: f0a00e81b093823b15055dee428569d7:04649314f6f5295c @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


apply to ros2_control master API

Signed-off-by: Karsten Knese<EMAIL_ADDRESS>

using admin rights to fix master.


Automatic error report

Problem Description
What steps will reproduce the problem?

Just open spyder and it will not connect to kernel
Traceback
  File "/home/toni/anaconda3/lib/python3.6/site-packages/spyder/plugins/__init__.py", line 514, in <lambda>
    toggled=lambda checked: self.toggle_view(checked),
  File "/home/toni/anaconda3/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 725, in toggle_view
    self.create_new_client(give_focus=False)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 1038, in create_new_client
    self.connect_client_to_kernel(client)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/spyder/plugins/ipythonconsole.py", line 1073, in connect_client_to_kernel
    kc.start_channels(shell=True, iopub=True)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/qtconsole/kernel_mixins.py", line 43, in start_channels
    super(QtKernelClientMixin, self).start_channels(*args, **kw)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/jupyter_client/threaded.py", line 212, in start_channels
    self.shell_channel._inspect = self._check_kernel_info_reply
  File "/home/toni/anaconda3/lib/python3.6/site-packages/jupyter_client/client.py", line 143, in shell_channel
    socket, self.session, self.ioloop
  File "/home/toni/anaconda3/lib/python3.6/site-packages/jupyter_client/threaded.py", line 205, in ioloop
    self._ioloop = ioloop.IOLoop()
  File "/home/toni/anaconda3/lib/python3.6/site-packages/tornado/util.py", line 312, in __new__
    instance.initialize(*args, **init_kwargs)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/zmq/eventloop/ioloop.py", line 139, in initialize
    super(ZMQIOLoop, self).initialize(impl=impl, **kwargs)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/tornado/ioloop.py", line 845, in initialize
    super(PollIOLoop, self).initialize(**kwargs)
  File "/home/toni/anaconda3/lib/python3.6/site-packages/tornado/ioloop.py", line 357, in initialize
    self.make_current()
  File "/home/toni/anaconda3/lib/python3.6/site-packages/tornado/ioloop.py", line 315, in make_current
    assert asyncio is None
AssertionError

Package Versions

Spyder 3.2.7 ``
Python 3.6.4
Qt 5.6.2
PyQt5 5.6
Linux 3.16.0-5-amd64

Dependencies
pyflakes >=0.6.0 :  1.6.0 (OK)
pycodestyle >=2.3:  2.3.1 (OK)
pygments >=2.0   :  2.2.0 (OK)
pandas >=0.13.1  :  0.22.0 (OK)
numpy >=1.7      :  1.14.1 (OK)
sphinx >=0.6.6   :  1.7.1 (OK)
rope >=0.9.4     :  0.10.7 (OK)
jedi >=0.9.0     :  0.11.1 (OK)
psutil >=0.3     :  5.4.3 (OK)
nbconvert >=4.0  :  5.3.1 (OK)
sympy >=0.7.3    :  1.1.1 (OK)
cython >=0.21    :  0.27.3 (OK)
qtconsole >=4.2.0:  4.3.1 (OK)
IPython >=4.0    :  6.2.1 (OK)
pylint >=0.25    :  1.8.2 (OK)

Thanks for reporting. This is a duplicate of #6627 ; and in any case outside of Spyder's control. To fix for now, run conda install tornado=4.5.3 from the Anaconda Prompt/Terminal/shell (Windows/Mac/Linux) in the conda environment that Spyder is installed in.


Question: is it possible to disable dimming, make content above touchable, and scroll?

I'm trying to do something like on Google Maps, where the content above the bottom sheet is touchable, there is no dimming, and I can scroll the bottom sheet till it shows its whole content , and even further if there is a lot of content.
Is it possible on this library to have this behavior ?

The library functions primarily as a dialog, so the request behavior isn't supported easily. The view used in Google Maps is most likely not a dialog but apart of the layout. You can wrap your view in a CollapsingView and add it to your view and manipulate it yourself.

@Kennyc1012 Too bad.
Can you help me with this though?
I've tried doing it for a long time on other libraries, and still failed:
http://stackoverflow.com/q/34160423/878126

Heres the approach I would take if I were try to replicate the Google Maps app.
Activity A- The wrapping activity for the views. Would contain 2 fragments. The activity theme should extend from Theme.AppCompat.NoActionBar
Map Fragment- This is where the map view would be held and manipulated. There should NO actionbar/toolbar here
Bottomsheet Fragment-  This is where the actionbar/toolbar will be. The fragment will be added with a transaction when wanting to me shown. Upon dismissing by either the back arrow or dragging, the fragment should be removed from the fragment manager.
If communication is needed between both fragments and/or with the parent activity, you can create an interface that the activity will implement and the fragments can make calls to the interface(Activity A) which can then communicate down to either or both of the fragments.

The activity and fragments part is ok and I can already customize it, but I don't get how to use the bottom sheet itself (which is why I try out multiple libraries that support bottom sheet).
in a POC, I've tried now using the CollapsingView inside the layout of the activity, as such:
<FrameLayout
             android:layout_width="match_parent"
             android:layout_height="match_parent">

    <TextView
        android:layout_width="match_parent"
        android:layout_height="match_parent"
        android:gravity="center"
        android:text="some normal content behind the bottom sheet, not a part of it"/>

    <com.kennyc.bottomsheet.CollapsingView
        android:layout_width="match_parent"
        android:layout_height="wrap_content">

        <include layout="@layout/custom_view"/>

    </com.kennyc.bottomsheet.CollapsingView>
</FrameLayout>

The "custom_view" layout is a large one, which also includes CollapsingToolbarLayout.
Yet, the bottom sheet takes the whole screen from the beginning. Isn't there a function to tell it to take the space of a certain view within or something? Only when scrolling, it should take the whole screen...

The CollapsingView will wrap to the whole views total height, not partially show it. I don't think this library is a good solution for what you need, sorry.

Too bad. Thank you for your help.
If you do know how to handle it well, please let me know.
Bottom sheet is supposed to initially show only a part of it. That's why it's also called "bottom"...

This can be achieved using the BottomSheetBehavior in the V23.2.0 support library described here


Jest/storybook/storyshots error el.getNode is not a function

Current behaviour

I'm trying to take snapshots of components using react native storybook storyshots
After adding the react-native-reanimated mocks using:
jest.mock('react-native-reanimated', () => require('react-native-reanimated/mock'));

There is one error left, getting:
TypeError: el.getNode is not a function

      at ref (node_modules/react-native-tab-view/lib/commonjs/TabBar.tsx:391:15)
      at commitAttachRef (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:9593:7)
      at commitAllLifeCycles (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:10834:7)
      at HTMLUnknownElement.callCallback (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2377:14)
      at invokeEventListeners (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:193:27)
      at HTMLUnknownElementImpl._dispatch (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:119:9)
      at HTMLUnknownElementImpl.dispatchEvent (node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:82:17)
      at HTMLUnknownElementImpl.dispatchEvent (node_modules/jsdom/lib/jsdom/living/nodes/HTMLElement-impl.js:30:27)
      at HTMLUnknownElement.dispatchEvent (node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:157:21)
      at Object.invokeGuardedCallbackDev (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2427:16)
      at invokeGuardedCallback (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:2480:31)
      at commitRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:11041:7)
      at node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12492:5
      at Object.unstable_runWithPriority (node_modules/scheduler/cjs/scheduler.development.js:255:12)
      at completeRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12491:13)
      at performWorkOnRoot (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12420:9)
      at performWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12328:7)
      at performSyncWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12302:3)
      at requestWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12171:5)
      at scheduleWork (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:11986:5)
      at scheduleRootUpdate (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12585:3)
      at updateContainerAtExpirationTime (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12613:10)
      at updateContainer (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:12624:10)
      at create (node_modules/react-test-renderer/cjs/react-test-renderer.development.js:13057:5)
      at getRenderedTree (node_modules/@storybook/addon-storyshots/dist/frameworks/react/renderTree.js:22:16)
      at node_modules/@storybook/addon-storyshots/dist/test-bodies.js:21:18
      at Object.<anonymous> (node_modules/@storybook/addon-storyshots/dist/api/snapshotsTestsTemplate.js:35:33)

Also there is this from yellowbox:
The above error occurred in the <ScrollViewMock> component:
          in ScrollViewMock (at TabBar.tsx:364)
          in View (created by View)
          in View (at TabBar.tsx:363)
          in View (created by View)
          in View (at TabBar.tsx:330)
          in TabBar (created by Pager)
          in Pager (at TabView.tsx:126)
          in View (created by View)
          in View (at TabView.tsx:125)
          in TabView (created by FriendList)
          in View (created by View)
          in View (at View.js:9)
          in ViewNB (created by Styled(ViewNB))
          in Styled(ViewNB) (created by FriendList)
          in FriendList (created by FriendsRoute)
          in View (created by View)
          in View (at View.js:9)
          in ViewNB (created by Styled(ViewNB))
          in Styled(ViewNB) (created by FriendsRoute)
          in FriendsRoute (created by SceneComponent)
          in SceneComponent (at SceneMap.tsx:16)
          in View (created by View)
          in View (at SceneView.tsx:92)
          in SceneView (at TabView.tsx:165)
          in View (created by View)
          in View (at Pager.tsx:667)
          in PanGestureHandler (at Pager.tsx:659)
          in Pager (at TabView.tsx:126)
          in View (created by View)
          in View (at TabView.tsx:125)
          in TabView (created by MainScreen)
          in View (created by View)
          in View (at View.js:9)
          in ViewNB (created by Styled(ViewNB))
          in Styled(ViewNB) (created by MainScreen)
          in BVLinearGradient (created by _class)
          in _class (created by LinearGradient)
          in LinearGradient (created by MyMainGradient)
          in View (created by View)
          in View (created by ImageBackground)
          in ImageBackground (created by MyMainGradient)
          in View (created by View)
          in View (created by MyMainGradient)
          in MyMainGradient (created by glamorous(MyMainGradient))
          in glamorous(MyMainGradient) (created by MainScreen)
          in MainScreen

Looks like ScrollViewMock is correctly used, I'm not sure why the el.getNode function isn't there. I'm not able to find any related errors reported upstream in react-native, and I assume there would reports for this - it should be relatively common to work with.
Expected behaviour
Should not error, I'm not sure whether some mock is missing that could be provided.
Code sample

What have you tried
Added react-native-reanimated mocks, this is the only error left.
The error is here: https://github.com/react-native-community/react-native-tab-view/blob/master/src/TabBar.tsx#L391
It seems that el.getNode is undefined in the jest/mock context.
Any ideas?
Your Environment

software
version

react-native
0.59.10

react-native-tab-view
2.9.0

react-native-gesture-handler
1.2.1

react-native-reanimated
1.1.0

Replacing the offending code with this.scrollView = el && (el.getNode ? el.getNode() : el); made it work.
I found some possibly related info about this here: https://github.com/facebook/react-native/issues/19650
I'm not familiar with .getNode(). I assume it's on Animated.ScrollView, but in the mock context a normal mocked ScrollView is used, which doesn't have that method.
Would this be a correct fix? Should I send a PR?

Seems that the Animated.ScrollView is replaced with a regular ScrollView by the react-native-reanimated mock here: https://github.com/kmagiera/react-native-reanimated/blob/master/mock.js#L35


Massive Repository overhaul & Unit Test Clean-up

Having looked at the IRepository implementation, I decided to make the change to leave the Entities unlinked from their respective DTO classes. This makes them Loose Coupled
I have also done some refactoring/Clean-Up on all Unit Tests.
I have Merged Juanro's Exception Handling Middleware into this branch as I had to resolve some merge conflicts.

@EduanO ran front end, ran test explorer, did a quick review, all seems fine.


Unable to set the SearchMode on a "mixed" Fhir Resource collection (when _include and _revinclude are specified) on Hapi Fhir Plain Server (with Paging and custom IBundleProvider)

NOTE: Before filing a ticket, please see the following URL:
https://github.com/hapifhir/hapi-fhir/wiki/Getting-Help
Describe the issue
With Hapi Fhir Reference Implementation, I can issue this request:
http://hapi.fhir.org/baseR4/Observation?_revinclude=Provenance%3Atarget
As expected, I get:
Observation(s) with

            "search": {
                "mode": "match"
            }

and for any includes or revincludes, I get
            "search": {
                "mode": "include"
            }

..........
With Hapi Fhir Plain Server, I have my own
public final class MyCustomBundleProvider implements IBundleProvider, Serializable {

@Override
public List<IBaseResource> getResources(int fromIndex, int toIndex) {

as documented here.
https://hapifhir.io/hapi-fhir/docs/server_plain/paging.html
Currently, I am populating the
List<IBaseResource>
(aka, the return object on the method)
with a mixture of Observation(s) and Provenance(s).
However, I do not see how to "tack on" the
            "search": {
                "mode": "include or match here of course"
            }

The object model has this (which I understand it)
Bundle.BundleEntryComponent bec = new Bundle.BundleEntryComponent();
bec.setResource(entry);
bec.getSearch().setMode(Bundle.SearchEntryMode.INCLUDE); /* or MATCH */

But the IBundleProvider (getResources) does not return a collection of Bundle.BundleEntryComponent, it returns a collection of IBaseResource(s).
Feature Request:
Be able to use (custom) IBundleProvider and set the search-mode on the "mixed" items in the return.
Environment (please complete the following information):
hapiFhirVersion = '5.5.1'
Additional context
Add any other context about the problem here.
`
package ca.uhn.fhir.rest.api.server;

public interface IBundleProvider {

/**
 * Load the given collection of resources by index, plus any additional resources per the
 * server's processing rules (e.g. _include'd resources, OperationOutcome, etc.). For example,
 * if the method is invoked with index 0,10 the method might return 10 search results, plus an
 * additional 20 resources which matched a client's _include specification.
 *

 * Note that if this bundle provider was loaded using a
 * page ID (i.e. via {@link ca.uhn.fhir.rest.server.IPagingProvider#retrieveResultList(RequestDetails, String, String)}
 * because {@link #getNextPageId()} provided a value on the
 * previous page, then the indexes should be ignored and the
 * whole page returned.
 *

 *
 * @param theFromIndex The low index (inclusive) to return
 * @param theToIndex   The high index (exclusive) to return
 * @return A list of resources. The size of this list must be at least theToIndex - theFromIndex.
 */
@Nonnull
List<IBaseResource> getResources(int theFromIndex, int theToIndex);

`

Hello, is there any update or workaround on this issue?

It looks like I have found the answer myself:
result.stream().peek(r -> ResourceMetadataKeyEnum.ENTRY_SEARCH_MODE.put(r, BundleEntrySearchModeEnum.MATCH)).collect(Collectors.toList())


'PyQt6.QtWebEngineCore' issue

I'm facing this issue
And where should I create the .env file can you be more specific?

The .env should be placed on the project root.
Can you please share the exact python version you are using for this?

I'm using python3 at this moment

It requires python 3.10 or above atm. Can you try with python3.10?
Let me know if it worksfor you. Thanks!


Refactor fix create enabled

Pull Request (PR) description

This Pull Request (PR) fixes the following issues

Task list

[ ] Added an entry under the Unreleased section in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[ ] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #1 into fix-create-enabled will increase coverage by 1%.
The diff coverage is 99%.

@@                Coverage Diff                 @@
##           fix-create-enabled     #1    +/-   ##
==================================================
+ Coverage                  88%    89%    +1%
==================================================
  Files                      20     20
  Lines                    1921   2080   +159
  Branches                   10     10
==================================================
+ Hits                     1698   1870   +172
+ Misses                    213    200    -13
  Partials                   10     10


React Native: java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule

Hello everyone, I do not use WebSocketModule but gives this error, please help.

3	09:42:20.822	unknown:ReactContextBaseJavaModule	Unhandled SoftException
java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule
	at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
	at com.facebook.react.modules.websocket.WebSocketModule.sendEvent(WebSocketModule.java:62)
	at com.facebook.react.modules.websocket.WebSocketModule.access$100(WebSocketModule.java:40)
	at com.facebook.react.modules.websocket.WebSocketModule$1.onMessage(WebSocketModule.java:190)
	at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:322)
	at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)
	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105)
	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:273)
	at okhttp3.internal.ws.RealWebSocket$1.onResponse(RealWebSocket.java:209)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
	at java.lang.Thread.run(Thread.java:764)

I have same issue too. Any clue how to get rid this error ?
Here my development env.
System:
    OS: macOS 10.15.5
    CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
    Memory: 206.95 MB / 8.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 14.4.0 - /usr/local/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.2
      System Images: android-28 | Intel x86 Atom_64
      Android NDK: 17.1.4828580
  IDEs:
    Android Studio: Not Found
    Xcode: 11.5/11E608c - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_131 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: Not Found
    react-native: * => 0.63.0
  npmGlobalPackages:
    *react-native*: Not Found

I have the same issue and pretty much the same development env. Anybody know of solutions?

I also get this issue, when running directly on my android TV (8.0), but not in the emulator. It occurs when it tries to fetch(). The error is identical as those above, and repeats 6 times in a row. The fetch promise is not rejected, and the error is only visible when watching logcat.
    OS: Windows 10 10.0.18363
    CPU: (8) x64 AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx
    Memory: 7.63 GB / 15.44 GB
  Binaries:
    Node: 14.6.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.14.6 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 26, 28, 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.1
      System Images: android-26 | Android TV Intel x86 Atom, android-26 | Google APIs Intel x86 Atom, android-29 | Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>26763
  Languages:
    Java: 1.8.0_262 - C:\Program Files\AdoptOpenJDK\jdk-8.0.262.10-hotspot\bin\javac.EXE
    Python: 3.8.5 - C:\Program Files (x86)\Python38-32\python.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

It seems that my issue was solved by fixing an instance of a chained ".then(SomeClass.callback)" from the fetch request, where the callback method was not a static member of SomeClass. No JS errors or warnings appeared for me telling me that callback didn't exist on the class (it did exist as a static member of the enclosing class, however). Once I tracked this mistake down, I no longer get the exception above. The runtime exception may have been triggered by the promise chain being invalid due to this mistake, but then I'm not sure why a more relevant error wasn't tripped in js linting or even at runtime, and ended up triggering a lower level exception instead.

I'm having the same problem when setting up a project on a new RN 0.63 base:
2020-07-27 14:58:12.930 7877-7929/? E/unknown:ReactContextBaseJavaModule: Unhandled SoftException
    java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by NativeAnimatedModule
        at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
        at com.facebook.react.animated.NativeAnimatedModule.initialize(NativeAnimatedModule.java:128)
        at com.facebook.react.bridge.ModuleHolder.doInitialize(ModuleHolder.java:236)
        at com.facebook.react.bridge.ModuleHolder.create(ModuleHolder.java:201)
        at com.facebook.react.bridge.ModuleHolder.getModule(ModuleHolder.java:156)
        at com.facebook.react.bridge.JavaModuleWrapper.getModule(JavaModuleWrapper.java:56)
        at com.facebook.react.bridge.JavaModuleWrapper.getConstants(JavaModuleWrapper.java:126)
        at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
        at android.os.Handler.handleCallback(Handler.java:883)
        at android.os.Handler.dispatchMessage(Handler.java:100)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
        at android.os.Looper.loop(Looper.java:214)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
        at java.lang.Thread.run(Thread.java:919)
2020-07-27 14:58:13.173 7877-7929/? E/ReactNativeJNI: logMarker RUN_JS_BUNDLE_END
2020-07-27 14:58:13.234 7877-7951/? E/unknown:ReactContextBaseJavaModule: Unhandled SoftException
    java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule
        at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
        at com.facebook.react.modules.websocket.WebSocketModule.sendEvent(WebSocketModule.java:62)
        at com.facebook.react.modules.websocket.WebSocketModule.access$100(WebSocketModule.java:40)
        at com.facebook.react.modules.websocket.WebSocketModule$1.onOpen(WebSocketModule.java:156)
        at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:210)
        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:919)

Note that I'm still using the default app code from npx react-native init project
I've just installed some modules so far...
My RN info:
$ npx react-native info
info Fetching system and libraries information...
System:
    OS: macOS Mojave 10.14.6
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
    Memory: 990.65 MB / 16.00 GB
    Shell: 3.2.57 - /bin/bash
  Binaries:
    Node: 14.1.0 - ~/.nvm/versions/node/v14.1.0/bin/node
    Yarn: 1.22.4 - /usr/local/bin/yarn
    npm: 6.14.4 - ~/.nvm/versions/node/v14.1.0/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.8.4 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
    Android SDK:
      API Levels: 18, 23, 24, 25, 26, 27, 28, 29
      Build Tools: 23.0.1, 23.0.3, 25.0.0, 25.0.2, 25.0.3, 26.0.0, 26.0.1, 26.0.2, 26.0.3, 27.0.3, 28.0.2, 28.0.3, 29.0.0, 29.0.2
      System Images: a...google_apis | Google APIs Intel x86 Atom Sys..., a...google_apis | Google APIs Intel x86 Atom Sys..., a... | Intel x86 Atom_64, a...google_apis | Google APIs Intel x86 Atom Sys..., a...gle_apis | Google APIs Intel x86 Atom_64 ..., a...-28 | Intel x86 Atom, a... | Intel x86 Atom_64, a...google_apis | Google APIs Intel x86 Atom Sys..., a...-29 | Intel x86 Atom, a... | Intel x86 Atom_64, a...google_apis | Google APIs Intel x86 Atom Sys...
      Android NDK: 20.1.5948944
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>00203
    Xcode: 11.2.1/11B53 - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_202-release - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

My react-native info:

this is happening with me too on 0.63.2 , it started after installing react-native-community/webview

Same issue on RN 0.63.2

same issue on RN 0.62.2

same issue on RN 0.62.2

Same here. Cant find a solution...
mine is related with @react-native-firebase/database connections
private void addOnceValueEventListener(ReactNativeFirebaseDatabaseQuery databaseQuery, Promise promise) {
    ValueEventListener onceValueEventListener = new ValueEventListener() {
      @Override
      public void onDataChange(@Nonnull DataSnapshot dataSnapshot) {
        Tasks.call(getExecutor(), () -> snapshotToMap(dataSnapshot))
          .addOnCompleteListener(task -> {
....

Anyone from this thread was able to solve the problem or have more info, please?

+1

+1

+1

Just happen on Android 5 API 21.
Works perfect on Android 10.

Having this issue with react native 0.63.2. Any help is appreciated.

Same here

The problem has not been resolved yet.

I have the same problem when I tried to integrate Stripe custom component to a RN app. When I fire the action of the component from an Android native button every thing works fine. But the project requires that the action will be fired from a RN button, is when I got this error. I'm using Android 10 as SDK developer tool. When this error occurs, immediately appears some other errors, that I don know its related to the first one, here the error that appears after:
2020-09-29 11:21:05.455 8076-8121/com.example.reactnativestripe E/unknown:ReactNative: Exception in native call
android.view.InflateException: Binary XML file line #24: Binary XML file line #24: Error inflating class
Caused by: android.view.InflateException: Binary XML file line #24: Error inflating class
Caused by: java.lang.reflect.InvocationTargetException
at java.lang.reflect.Constructor.newInstance0(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
at android.view.LayoutInflater.createView(LayoutInflater.java:647)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:790)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:730)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:863)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:866)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
at com.stripe.android.databinding.CardInputWidgetBinding.inflate(CardInputWidgetBinding.java:88)
at com.stripe.android.view.CardInputWidget.(CardInputWidget.kt:49)
at com.stripe.android.view.CardInputWidget.(CardInputWidget.kt:47)
at com.reactnativestripe.checkout.CheckoutView.(CheckoutView.kt:34)
at com.reactnativestripe.checkout.CheckoutView.(CheckoutView.kt:18)
at com.reactnativestripe.CheckoutModule.getToken(CheckoutModule.kt:31)
at java.lang.reflect.Method.invoke(Native Method)
at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:151)
at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
at android.os.Looper.loop(Looper.java:193)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
at java.lang.Thread.run(Thread.java:764)
Caused by: java.lang.IllegalArgumentException: The style on this component requires your app theme to be Theme.AppCompat (or a descendant).
at com.google.android.material.internal.ThemeEnforcement.checkTheme(ThemeEnforcement.java:248)
at com.google.android.material.internal.ThemeEnforcement.checkAppCompatTheme(ThemeEnforcement.java:218)
at com.google.android.material.internal.ThemeEnforcement.checkCompatibleTheme(ThemeEnforcement.java:153)
at com.google.android.material.internal.ThemeEnforcement.obtainTintedStyledAttributes(ThemeEnforcement.java:120)
at com.google.android.material.textfield.TextInputLayout.(TextInputLayout.java:424)
at com.google.android.material.textfield.TextInputLayout.(TextInputLayout.java:396)
at java.lang.reflect.Constructor.newInstance0(Native Method)
at java.lang.reflect.Constructor.newInstance(Constructor.java:343)
at android.view.LayoutInflater.createView(LayoutInflater.java:647)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:790)
at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:730)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:863)
at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:824)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:866)
at android.view.LayoutInflater.inflate(LayoutInflater.java:489)
at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
at android.view.LayoutInflater.inflate(LayoutInflater.java:374)
at com.stripe.android.databinding.CardInputWidgetBinding.inflate(CardInputWidgetBinding.java:88)
at com.stripe.android.view.CardInputWidget.(CardInputWidget.kt:49)
at com.stripe.android.view.CardInputWidget.(CardInputWidget.kt:47)
at com.reactnativestripe.checkout.CheckoutView.(CheckoutView.kt:34)
at com.reactnativestripe.checkout.CheckoutView.(CheckoutView.kt:18)
at com.reactnativestripe.CheckoutModule.getToken(CheckoutModule.kt:31)
at java.lang.reflect.Method.invoke(Native Method)
at com.facebook.react.bridge.JavaMethodWrapper.invoke(JavaMethodWrapper.java:372)
at com.facebook.react.bridge.JavaModuleWrapper.invoke(JavaModuleWrapper.java:151)
at com.facebook.react.bridge.queue.NativeRunnable.run(Native Method)
at android.os.Handler.handleCallback(Handler.java:873)
at android.os.Handler.dispatchMessage(Handler.java:99)
at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)
at android.os.Looper.loop(Looper.java:193)
at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)
at java.lang.Thread.run(Thread.java:764)
2020-09-29 11:21:05.601 8076-8076/com.example.reactnativestripe E/unknown:ReactContextBaseJavaModule: Unhandled SoftException
java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by AppState
at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
at com.facebook.react.modules.appstate.AppStateModule.sendEvent(AppStateModule.java:96)
at com.facebook.react.modules.appstate.AppStateModule.onWindowFocusChange(AppStateModule.java:86)
at com.facebook.react.bridge.ReactContext.onWindowFocusChange(ReactContext.java:300)
at com.facebook.react.ReactInstanceManager.onWindowFocusChange(ReactInstanceManager.java:747)
at com.facebook.react.ReactActivityDelegate.onWindowFocusChanged(ReactActivityDelegate.java:153)
at com.facebook.react.ReactActivity.onWindowFocusChanged(ReactActivity.java:120)
at androidx.appcompat.view.WindowCallbackWrapper.onWindowFocusChanged(WindowCallbackWrapper.java:124)
at com.android.internal.policy.DecorView.onWindowFocusChanged(DecorView.java:1518)
at android.view.View.dispatchWindowFocusChanged(View.java:12766)
at android.view.ViewGroup.dispatchWindowFocusChanged(ViewGroup.java:1456)
at android.view.ViewRootImpl.handleWindowFocusChanged(ViewRootImpl.java:2581)
at android.view.ViewRootImpl.access$900(ViewRootImpl.java:132)
at android.view.ViewRootImpl$ViewRootHandler.handleMessage(ViewRootImpl.java:4175)
at android.os.Handler.dispatchMessage(Handler.java:106)
at android.os.Looper.loop(Looper.java:193)
at android.app.ActivityThread.main(ActivityThread.java:6669)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)

Any update here?

Same here with 0.62.2

same issue with 0.63.3

same issue when upgrade to 0.63.3

have the same issue, I solved mine by opening my code editor manually instead of opening my app in the terminal. For example, when I do open my code editor in git bash using code .  to open VS Code. And then inside VS Code terminal I typed start cmd to open cmd terminal again. And then again I typed react-native start in the CMD terminal to start my server.
However, there's a pattern, git bash ---> VS Code ---> CMD
So I do a little experiment to prove my assumption that this kind of pattern, inherited the backend services of the parent or root I do no which one (I'm no expert but), I suspect that git bash or VS Code is affecting my react native server.
So I did open VS Code or my Code editor manually, and open my project manually using Open Folder option instead of opening it in the terminal. However, these are my own problem domain, but I just want to share it to you so you can have an idea

have the same issue, I solved mine by opening my code editor manually instead of opening my app in the terminal. For example, when I do open my code editor in git bash using code .  to open VS Code. And then inside VS Code terminal I typed start cmd to open cmd terminal again. And then again I typed react-native start in the CMD terminal to start my server.
However, there's a pattern, git bash ---> VS Code ---> CMD
So I do a little experiment to prove my assumption that this kind of pattern, inherited the backend services of the parent or root I do no which one (I'm no expert but), I suspect that git bash or VS Code is affecting my react native server.
So I did open VS Code or my Code editor manually, and open my React Native project manually using Open Folder option instead of opening it in the terminal and it worked. However, these are my own problem domain, but I just want to share it to you so you can have an idea

The exception being discussed in this thread is displayed in the logcat and then the app crashes with the below c++ error.
The below crash is happening every time we reload the JS code either using the "Reload" option from debug menu (or) by clicking cmd+r on the metro server.
Can anyone suggest if the exception and crash are related?
    --------- beginning of crash A/libc: Fatal signal 6 (SIGABRT), code -1 (SI_QUEUE) in tid 10233 (pool-18-thread-), pid 9986 E/libc++abi: terminating with uncaught exception of type std::runtime_error: logging not available for section entry E/libc++abi: terminating with uncaught exception of type std::runtime_error: logging not available for section entry

same issue with 0.63.3

same issue with 0.62.2

Same issue here with react-native 0.63.0 and Xiaomi in development environment.
I tried with Huawei and still works

Same issue.
App still running as normal but the errors show continuously.
RN 0.63.4
Some users crash right after open app, I don't know if this is the reason or not.

Any solved the issue .Iam getting same use while using react-native-google-fit.
while calling getActivitySamples function .

Any solved the issue .Iam getting same use while using react-native-google-fit.
while calling getActivitySamples function .

while calling getActivitySamples function .

same here

Connecting mobile device to the same wifi network as pc resolved this for me

same problem

Same here.

I used to get this error when trying to do send over a websocket which has being closed already. In real-world it often happens that a socket gets open and then closes almost immediatelly (within a few milliseconds) due to poor network connection or something.
So, watch for socket close and as it happens, update your state so that you won’t even try send’ing over it. Also, on connection give the websocket some time to “cooldown”, i.e. do nothing, but watch for close events.
Hope this helps.

Same error. After testing, I found the reason cause the issue, I called ReactInstanceManager.recreateReactContextInBackground method multiple times in Application.onConfigurationChanged(Configuration).

Same error here!
In our case, the application gets stuck on the splash screen and goes into a reload loop

Logcat:

Environment:
System:
    OS: Windows 10 10.0.18363
    CPU: (4) x64 Intel(R) Core(TM) i7-6500U CPU @ 2.50GHz
    Memory: 1.80 GB / 11.90 GB
  Binaries:
    Node: 14.15.4 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.4 - C:\XXX\node_modules\.bin\yarn.CMD
    npm: 6.14.10 - C:\Program Files\nodejs\npm.CMD
    Watchman: Not Found
  SDKs:
    Android SDK:
      API Levels: 23, 25, 26, 27, 28, 29
      Build Tools: 23.0.1, 26.0.3, 27.0.3, 28.0.3, 29.0.2
      System Images: android-28 | Intel x86 Atom_64, android-28
| Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
      Android NDK: Not Found
  IDEs:
    Android Studio: Version  <IP_ADDRESS> AI-191.8<IP_ADDRESS>00203
  Languages:
    Java: Not Found
    Python: 2.7.17 - C:\Python27\python.EXE
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Same issue with 0.64.0 :(

I just started running into this issue on an AndroidTV build.
I tried to trace back all sorts of stuff, and after reverting axios from 0.21.1 to 0.18.3 - the error stopped occurring.

Hey everyone, started getting this error when using apollo client. The strange thing is that i have been using it without trouble for a long time and from all of a sudden this error appears :/

Same error with RN v0.64.0

For people still having trouble, I actually found out the real culprit, at least in my case.
A network call was being done in a the root component, in the constructor - which caused this issue.

If could help, I was getting this error when I removed apply plugin: 'com.google.gms.google-services'  from the build.gradle, but it was still required from react-native-firebase installed as js dependency.

Same issue on Expo Bare workflow RN 0.63.4
    OS: macOS 11.2
    CPU: (8) x64 Apple M1
    Memory: 453.00 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 12.18.4 - /usr/local/opt/node@12/bin/node
    Yarn: 1.22.5 - /usr/local/bin/yarn
    npm: 6.14.6 - /usr/local/opt/node@12/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.3 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 14.4, DriverKit 20.2, macOS 11.1, tvOS 14.3, watchOS 7.2
    Android SDK:
      API Levels: 29, 30
      Build Tools: 28.0.3, 29.0.2, 30.0.2
      System Images: android-29 | Google APIs Intel x86 Atom, android-30 | Google APIs Intel x86 Atom, android-S | Google APIs ARM 64 v8a
      Android NDK: Not Found
  IDEs:
    Android Studio: 4.1 AI-201.87<IP_ADDRESS>99119
    Xcode: 12.4/12D4e - /usr/bin/xcodebuild
  Languages:
    Java: 1.8.0_265 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.13.1 => 16.13.1
    react-native: ~0.63.4 => 0.63.4
    react-native-macos: Not Found
  npmGlobalPackages:

Got the same setup as @pjay79 , trying to dig into the AppRegistry.js, 'LogBox' is registered and run, it seems the next to run is the app, but it crashes right before it. Downgraded axios from 0.21.1 to 0.18.1, still stuck. not sure how to trace that any further

Getting same error here, but oddly only one tester out of three reports it, and that user reports it consistently. We're not using websockets within the app.
React Native 0.64.1.
2021-05-31 18:07:18.001 13515-16273/com.company.transfers E/unknown:ReactContextBaseJavaModule: Unhandled SoftException
    java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule
        at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
        at com.facebook.react.modules.websocket.WebSocketModule.sendEvent(WebSocketModule.java:62)
        at com.facebook.react.modules.websocket.WebSocketModule.access$100(WebSocketModule.java:40)
        at com.facebook.react.modules.websocket.WebSocketModule$1.onMessage(WebSocketModule.java:187)
        at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:322)
        at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)
        at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105)
        at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:273)
        at okhttp3.internal.ws.RealWebSocket$1.onResponse(RealWebSocket.java:209)
        at okhttp3.RealCall$AsyncCall.execute(RealCall.java:174)
        at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
        at java.lang.Thread.run(Thread.java:919)

I was getting the same error in Android Studio LogCat. My app was stacking on splash screen with no errors in logs or on the phone, only this message in LogCat. I've calculated the line, which caused this error - call of NativeModule method.
To find the error I've wrapped native method call with InteractionManager.runAfterInteractions and the error appeared as habitual red box, saying "Cannot have a non-function arg after a function arg".
Hope this trick will help you to find out the error.

same  0.64.2

Getting the same error on upgrade to React Native 0.64.1. The error only occurs when the Android interface is first opened. The screen is stuck on a white page.
Rotating the device, however, loads the interface correctly.

The ws protocol reports this error on some models, and everything is normal after changing to the wss protocol

Same error with RN v0.64.2

In my case =>
We are using react-native web view, and we have different microservices and we need to connect these services together. We are giving ports to build. In local env, I gave, localhost:3000 and it returned this error. When I search on google I found these solutions on StackOverflow. And these ones worked for me. In Android, they do not accept http://localhost:3000 you have to fill it like WEB_HOST=http://<IP_ADDRESS>:3000
Maybe it helps someone
https://stackoverflow.com/questions/6760585/accessing-localhostport-from-android-emulator

Facing same issue in android, please suggest any solution.

00

this issue is not happening only in android emulator in real device also happening so not useful !

In my case =>
We are using react-native web view, and we have different microservices and we need to connect these services together. We are giving ports to build. In local env, I gave, localhost:3000 and it returned this error. When I search on google I found these solutions on StackOverflow. And these ones worked for me. In Android, they do not accept http://localhost:3000 you have to fill it like WEB_HOST=http://<IP_ADDRESS>:3000
Maybe it helps someone
https://stackoverflow.com/questions/6760585/accessing-localhostport-from-android-emulator

this issue is not happening only in android emulator in real device also happening so not useful !

Unfortunately, there is no solution yet.

Same error with RN v0.64.2.
In my case, It seems that the socket connection is established successfully, but the specific sending content is reported as an error.
I collected the logs of Android log cat，it says:
09-03 10:37:13.054 I/ReactNativeJS(16467): [NIM LOG 09-03 10:37:13:053 IM]  protocol::sendCmd: login
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): Unhandled SoftException
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by WebSocketModule
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:67)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at com.facebook.react.modules.websocket.WebSocketModule.sendEvent(WebSocketModule.java:62)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at com.facebook.react.modules.websocket.WebSocketModule.access$100(WebSocketModule.java:40)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at com.facebook.react.modules.websocket.WebSocketModule$1.onMessage(WebSocketModule.java:190)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.internal.ws.RealWebSocket.onReadMessage(RealWebSocket.java:323)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.internal.ws.WebSocketReader.readMessageFrame(WebSocketReader.java:219)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:105)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:203)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
09-03 10:37:13.091 E/unknown:ReactContextBaseJavaModule(16467): 	at java.lang.Thread.run(Thread.java:929)

Can anyone help？

Same thing here. We're on v0.63 with Expo-managed workflow and using SocketCluster client. Has anybody been able to resolve this issue?
I was thinking if it could be related to usesCleartextTraffic property, but haven't found yet how to enable it in Expo.

I'm getting this error when I enable StoryBook not sure what started it though.

Have similar issue, but the error appeared not only due to WebSocketModule  but AppState, Device Info, Fresco Module, DialogManagerAndroid.
All of it happened only after reloading the app in developer mode.

So I had the same issue but I've found a workaround thanks to this thread
https://stackoverflow.com/questions/40976910/react-native-module-lifecycle-dispose-resources-on-reload/55183043#55183043
Basically its an issue with react-native's hot reloading where it re-initialize the js side of the code and it's react modules with new instances but doesn't dispose the native modules and uses the old ones before the reload which causes some conflicts.
It doesn't fix the error entirely but it looks like it doesn't interfere with my app for now.

I have realized that wrong Firebase installation cause the error.
I have removed those changes from my /android/app/build.gradle file
implementation platform('com.google.firebase:firebase-bom:28.4.2')
implementation 'com.google.firebase:firebase-analytics'

You do not need those changes in the new version of Firebase. Works fine now

any solution?

any solution on this?

Yeah is bailable conception and nota is ay several problema inbrealiseds every effects inbthe data of the weeks. Is accepted and functionally.

Everyone - there's a workaround here courtesy of @oviedo97fer and it works for me!!
https://github.com/facebook/react-native/issues/31397#issuecomment-831262990

Same issue on RN 0.65.1
2022-01-12 16:54:26.395 12636-12736/com.myapp E/unknown:ReactContextBaseJavaModule: Unhandled SoftException     java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by DeviceInfo         at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:66)         at com.facebook.react.modules.deviceinfo.DeviceInfoModule.invalidate(DeviceInfoModule.java:114)         at com.facebook.react.bridge.ModuleHolder.destroy(ModuleHolder.java:110)         at com.facebook.react.bridge.NativeModuleRegistry.notifyJSInstanceDestroy(NativeModuleRegistry.java:108)         at com.facebook.react.bridge.CatalystInstanceImpl$1.run(CatalystInstanceImpl.java:359)         at android.os.Handler.handleCallback(Handler.java:883)         at android.os.Handler.dispatchMessage(Handler.java:100)         at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)         at android.os.Looper.loop(Looper.java:214)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)         at java.lang.Thread.run(Thread.java:919) 2022-01-12 16:54:26.395 12636-12736/com.myapp E/unknown:ReactContextBaseJavaModule: Unhandled SoftException     java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by AppState         at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:66)         at com.facebook.react.modules.appstate.AppStateModule.invalidate(AppStateModule.java:127)         at com.facebook.react.bridge.ModuleHolder.destroy(ModuleHolder.java:110)         at com.facebook.react.bridge.NativeModuleRegistry.notifyJSInstanceDestroy(NativeModuleRegistry.java:108)         at com.facebook.react.bridge.CatalystInstanceImpl$1.run(CatalystInstanceImpl.java:359)         at android.os.Handler.handleCallback(Handler.java:883)         at android.os.Handler.dispatchMessage(Handler.java:100)         at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)         at android.os.Looper.loop(Looper.java:214)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)         at java.lang.Thread.run(Thread.java:919) 2022-01-12 16:54:26.395 12636-12736/com.myapp E/unknown:ReactContextBaseJavaModule: Unhandled SoftException     java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by NativeAnimatedModule         at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:66)         at com.facebook.react.animated.NativeAnimatedModule.invalidate(NativeAnimatedModule.java:897)         at com.facebook.react.bridge.ModuleHolder.destroy(ModuleHolder.java:110)         at com.facebook.react.bridge.NativeModuleRegistry.notifyJSInstanceDestroy(NativeModuleRegistry.java:108)         at com.facebook.react.bridge.CatalystInstanceImpl$1.run(CatalystInstanceImpl.java:359)         at android.os.Handler.handleCallback(Handler.java:883)         at android.os.Handler.dispatchMessage(Handler.java:100)         at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)         at android.os.Looper.loop(Looper.java:214)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)         at java.lang.Thread.run(Thread.java:919) 2022-01-12 16:54:26.396 12636-12736/com.myapp E/unknown:ReactContextBaseJavaModule: Unhandled SoftException     java.lang.RuntimeException: Catalyst Instance has already disappeared: requested by FrescoModule         at com.facebook.react.bridge.ReactContextBaseJavaModule.getReactApplicationContextIfActiveOrWarn(ReactContextBaseJavaModule.java:66)         at com.facebook.react.modules.fresco.FrescoModule.invalidate(FrescoModule.java:202)         at com.facebook.react.bridge.ModuleHolder.destroy(ModuleHolder.java:110)         at com.facebook.react.bridge.NativeModuleRegistry.notifyJSInstanceDestroy(NativeModuleRegistry.java:108)         at com.facebook.react.bridge.CatalystInstanceImpl$1.run(CatalystInstanceImpl.java:359)         at android.os.Handler.handleCallback(Handler.java:883)         at android.os.Handler.dispatchMessage(Handler.java:100)         at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(MessageQueueThreadHandler.java:27)         at android.os.Looper.loop(Looper.java:214)         at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(MessageQueueThreadImpl.java:226)         at java.lang.Thread.run(Thread.java:919)

same error with RN 0.67.1
System:
OS: macOS 11.5.2
CPU: (8) x64 Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Memory: 4.53 GB / 32.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 14.18.1 - ~/.nvm/versions/node/v14.18.1/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 6.14.15 - ~/.nvm/versions/node/v14.18.1/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.2 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 15.0, DriverKit 20.4, macOS 11.3, tvOS 15.0, watchOS 8.0
Android SDK:
API Levels: 19, 22, 23, 24, 25, 26, 27, 28, 29, 30
Build Tools: 26.0.2, 27.0.3, 28.0.0, 28.0.3, 29.0.1, 29.0.2, 30.0.2
System Images: android-24 | Google Play Intel x86 Atom, android-25 | Google APIs ARM EABI v7a, android-26 | Google APIs Intel x86 Atom, android-26 | Google Play Intel x86 Atom, android-27 | Google APIs Intel x86 Atom
Android NDK: 20.0.5594570
IDEs:
Android Studio: 2020.3 AI-203.7717.56.2031.7935034
Xcode: 13.0/13A233 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_201 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.2 => 17.0.2
react-native: ^0.67.1 => 0.67.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found

Hello all, I was just updating from react-native 0.62.2 to 0.67.2 using https://react-native-community.github.io/upgrade-helper. I ran into this exact issue you all are describing. The solution for me was going through: https://reactnative.dev/docs/environment-setup
In there they say: "Android Studio installs the latest Android SDK by default. Building a React Native app with native code, however, requires the Android 10 (Q) SDK in particular"
I'm not sure if this applies to other RN versions, but this fixed it for me. I was using a device that was much higher than that. Instead I followed the instructions there, downloaded the appropriate tools and now am running fine on an emulator with API Q 29 successfully.
Some caveats (probably due to me still being in the middle of updating everything)—
The only way this works for me currently is by running it with $ yarn react-native run-android
If I just press play in Android Studio it does not work and gives me other errors. Specifically I have to have Android Studio open with the emulator running, and then I call $ yarn react-native run-android and everything works. Beyond that I'm not sure! Hope this helps some people, though I imagine this error occurs for a variety of reasons. I'm on a mac using the new M1 chip so there's all sorts of oddities to work through :)

Same issue on RN 0.67.4
any solution?

any success guys?

Hi guy, I success to fix this error by adding  "facebook_client_token"
Add this in strings.xml

56789
And add this in AndroidManifest
<meta-data android:name="com.facebook.sdk.ClientToken" android:value="@string/facebook_client_token"/>

facebook_client_token
what is app doesn't have any facebook_client_token  ?

Still happening

Never mind. I solved it by moving my toast component inside the safe view area provider. Maybe my response can be useful for someone

any success guys?

My issue was the request url was empty. 😬
What a time wasted.

My issue was the request url was empty. 😬 What a time wasted.
which URL??
Please advice

Same here, wrong URL passed to fetch. Check your fetch URLs.

Same here, wrong URL passed to fetch. Check your fetch URLs.

do you mean a regular fetch() in your code? I don't have one and still see the error

+1

The same issue on RN 0.66.3
any solution?

The same issue on RN 0.68.0
any solution, any help?

Same here, RN 0.68.2

Same here, RN 0.66.4

Did anyone find a solution?
RN 0.68.1

Any updates here?

Despite logging that it's an unhandled exception, it can safely be ignored. It's a whole bunch of noise related to removing listener references that's a bit out of order here.
Context:
When your catalyst instance (a.k.a. that bridge between JS and the Android runtime) goes to clean itself up, either out of spite or because you've decided to close the app, the teardown process is a bit out of order.
Every JS bridge module has this overrideable method called invalidate. Across nearly all of the React Native-owned modules is an implementation that looks like this: https://github.com/facebook/react-native/blob/1453ef1a8836ead03f66792bd36bfcde333434c0/ReactAndroid/src/main/java/com/facebook/react/modules/appstate/AppStateModule.java#L124-L131
They're all calling this nifty getReactApplicationContextIfActiveOrWarn method. And, under the hood, that method looks like this: https://github.com/facebook/react-native/blob/1453ef1a8836ead03f66792bd36bfcde333434c0/ReactAndroid/src/main/java/com/facebook/react/bridge/ReactContextBaseJavaModule.java#L54-L69
Notice, in particular, the top of that method where the check hasActiveReactInstance is made. This method returns true if and only if the Catalyst instance is non-null and not marked as destroyed.
This is perhaps where the error lies: before the catalyst even notifies all of the bridge methods that it's being destroyed, it marks itself as destroyed. Therefore, any subsequent checks on the catalyst instance being active will yield a false value: https://github.com/facebook/react-native/blob/1453ef1a8836ead03f66792bd36bfcde333434c0/ReactAndroid/src/main/java/com/facebook/react/bridge/CatalystInstanceImpl.java#L353-L360.
A potential solution would be to move that mDestroyed = true; assignment on line 353 to the very bottom of the runnable chain only after all teardown has occurred. But this ultimately makes no difference: the errors you are seeing is just noise and not actual exceptions. This is also a potential memory leak as we've begun to evaluate in our own app (having old modules hanging around in a list of listeners is the memory leak) but not serious enough unless you manually tear down the React Native catalyst instance on your own.

Still having this issue, it seems to be causing issues with endless animations when running Detox tests.
RN 70.2

Despite logging that it's an unhandled exception, it can safely be ignored.

I might be, but as of now this issue correlates with Detox and animation issues I'm experiencing.

Hello everyone,
I had also a similar issue "Unhandled SoftException". In my case, it was "just" a wrong input type... float instead of string.
As said before:  just before, it is something which append on native module implementation (so a lot of lib).
What I understand is that you can't handle these SoftException in case of lib. In case of custom native module, it is up to you to do so.
SoftExceptions are just the consequences of real not caught exceptions. React Native "catch" for you these exception to not propagade them to JS part and to not block the app. However, in some cases, it has the effect (in my case everything regarding App state and focus such as button press and touch).
You can, depending of the case, ignore or not ignore this exception.
Steps to fix the issue (as lib user):
1 - Try to find the JS function/promise which generate the issue
2 - Verify that function inputs and object's context are compliant with the needs of the function/promise . At least one of these two cases must be wrong
3 - Fix theses elements
A good practice is to always deal with input errors before using a function or a promise.
In JS, we have a wrong tendancy to let reject (in cas of promises) catching all errors cases such as a wrong input type or value.
However, in most of languages, it is up to the service consumer to deal with that.
As RN is build on theses languages, it means that the developer must have the same mindset.
If I take the example of the fetch function:
1 - you must first check that variable with the url is a string and is not an empty string
2 - call the fetch
3 - having your rejected callback to deal with errors happening on the "real process" such as network error.
Hope it can help.

In my case, the app was stuck on the splash screen. I was doing an upgrade of packages and had commented certain pieces of code during the upgrade. The app was stuck on the splash screen and in the logcat I was getting this error. There was some code that I accidentally commented which was responsible for hiding the splash screen. I uncommented that and my app started working again.

@sahil-kc Hi! Did you find any solution for this?

I encountered this issue where I was making API calls using HTTP while my backend was running on HTTPS.  Just a heads-up for anyone facing a similar issue.