unhandled promise rejection
please provide the following:

sdk version:“expo”: “~39.0.2”,

platforms(android/ios/web/all):all

hello, could you give me some recommendation to solve this error:

[unhandled promise rejection: error: no native splash screen registered for provided activity. please configure your application’s mai…
hola, acabo de solucionar mi problema

problema:

[unhandled promise rejection: error: no native splash screen registered for provided activity. please configure your application’s main activity to call ‘splashscreen.show’ ([https://github.com/expo/expo/tree/master/packages/expo-splash-screen#-config…](https://github.com/expo/expo/tree/master/packages/expo-splash-screen#-configure-android)
was caused because there was an "unhandled rejection error: eacces: permission denied, mkdir '/home//.npm/\_cache/index-<…>/

solved problem by just adding “sudo” in front

sudo npx create-react-app . try this version:

<https://drive.google.com/file/d/1ffegjdy1563skl8qrnxtcngwg4vra_7-/view?usp=sharing>

we’re still working through some compatibility issues with the new os. it seems if i use the framework version that solves some of the visual glitches it messes up camera compatibility. hey [@edgar.mtz](/u/edgar.mtz),

currently [interpretation](https://support.zoom.us/hc/en-us/articles/360034919791-language-interpretation-in-meetings-and-webinars) is not available on the web sdk.

here is a list of the supported features:

[image]

[web - native sdks - zoom software development kit (zoom sdk)](https://marketplace.zoom.us/docs/sdk/native-sdks/web#browser-support)

zoom web sdk

the web sdk enables the development of video applications powered by zoom's core framewo… hi [@tepper](/u/tepper),

[image] tepper:

i suspect this is because the feature is simply not offered on my phone

you are correct about that. the spam blocking feature you reference requires a newer republic compatible (a/k/a 3.0) phone using a my choice plan. the feature is not available for legacy repub… I believe they are working on adding Fresco to different platforms. As stated in [this thread](https://community.adobe.com/t5/fresco/fresco-compatibility/td-p/10893021?page=1) though there are no timeframes for release on other platforms. Fresco seems to have been specifically designed to work with pen technologies. So that's where the limitation lies as far as platform compatibility. use promise.allsettled(). the following code works, it's simply going to skip over the rejected promise:
```javascript
function getwikiprofiles(data) {
 const profiles = data.people.map(person => {
 return getjson(wikiurl + person.name);
 });
 return promise.allsettled(profiles);
}
function generatehtml(data) {
 //console.log(data);
 data.foreach(person => {
 if (person.status  'fulfilled') {
 person = person.value;
 const section = document.createelement('section');
 peoplelist.appendchild(section);
 section.innerhtml = 
 ![](%24%7bperson.thumbnail.source%7d)
${person.title}



${person.description}


${person.extract}


;
 }
 });
``` yeah this is me, that will break it even further.

you do not want the sshd template, no reason to be running sshd in your container.

look at your container config, (app.yml), delete the line with sshd it is legacy you do not need. we stopped using this pattern 3 or so years ago but forgot to remov… we believe this issue has been fixed with our most recent release, version 10.9.
 


 you can learn more here:
 



 please try updating, and let me know if you have any other questions.
 


  
 


 also, if you are experiencing this issue via the web client, please let us know here: Well just had TAC look into it. They restarted the management plane which fixed the issue.

The reason we believe was due to insufficient resource in the management plane at the time of the update.

Thanks Sandeep for your help.




[View solution in original post](/t5/general-topics/app-version-mismatch/m-p/45216#M33220) hey there,

a bunch of additional questions:

which version of blokada do you use right now? v.4.6.3 is the current one.

is private dns in your phone settings disabled? if not, please do disable it.

did you activate a dns in blokada?

did you enable traffic mode or data saver in your phone settings?

…