@37:959
value@37:2503
value@37:918
value@-1
value@-1
```
Here is a snippet showing how I’m trying to run the sdk:
App.tsx:
```auto
import React from 'react';
import { NavigationContainer, DarkTheme } from '@react-navigation/native';
import { ThemeProvider, USER_TYPE } from '@app/theme';
import AppNavigation from '@customer/navigation';
import { ApolloProvider } from '@apollo/client';
import { createClient } from '@zedapp/data-access';
import { useAuth } from '@customer/modules/auth/login/hooks/useAuth';
import SendBird from 'sendbird';
import Config from 'react-native-config';
import { chatVar } from '@customer/reactivities';
import ChatProvider from './context';
const sendbird = new SendBird({ appId: Config.SENDBIRD_APP_ID });
// chatVar({ sendbird });
sendbird.setErrorFirstCallback(true);
const initialState = {
sendbird,
};
const App = () => {
const { authVar } = useAuth();
const params = {
authToken: authVar.token,
};
const client = createClient(params);
return (
);
};
export default App;
```
and my chat screen (where i’m getting the error):
```auto
import React, { useEffect } from 'react';
import { StyleSheet } from 'react-native';
import { Container, Header, hp } from '@app/components';
import { useTheme } from '@app/theme';
import { useChatContext } from '@customer/app/context';
import { useCustomer } from '@customer/modules/profile/hooks/useCustomer';
const ChatWithAgentScreen = () => {
const theme = useTheme();
const { sendbird } = useChatContext();
const { customerVar } = useCustomer();
useEffect(() => {
// console.log(sendbird);
// if (sendbird.connect) connect();
connect();
}, []);
const connect = async () => {
try {
const user = await sendbird?.connect(customerVar?.idCustomerUser);
console.log('connect_user', user);
} catch (err) {
console.log('connect_error', err);
}
};
return (
<>
);
};
const styles = StyleSheet.create({
container: {
flex: 1,
marginBottom: hp(12),
backgroundColor: '#fff',
},
body: { paddingHorizontal: 24, justifyContent: 'center' },
moodSelector: {
marginVertical: 12,
},
});
export default ChatWithAgentScreen;
```
react native: 0.66.4
sendbird: 3.1.7
---
### Author:  [@Ian](https://community.sendbird.com/u/Ian)
#### Post date: [May 10, 2022, 8:07pm UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/3 "2022-05-10T20:07:27Z")
Hello @moe and welcome to the Sendbird community!
The exception you are receiving, `API dummy call failed`, indicates a network issue on the client side that is preventing the SDK from contacting the Sendbird server. Are you able to validate if your network is blocking traffic to Sendbird?
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 11, 2022, 6:11am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/4 "2022-05-11T06:11:23Z")
I’m not sure how to validate connectivity for sendbird, but other network requests are working fine. @Ian
---
### Author:  [@Tyler](https://community.sendbird.com/u/Tyler)
#### Post date: [May 11, 2022, 6:14am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/5 "2022-05-11T06:14:13Z")
Hi @moe,
Responding for Ian as I’m here during KST hours. Essentially, SDK makes a call to `https://api-{app_id}.sendbird.com` and looks to receive a 200 back (Ignore the actual data returned).
This is in order to test if it can connect to Sendbird to open a websocket connection. Ultimately, troubleshooting client side network issues from our side is rather difficult but one thing you could try is opening a web browser and make that same request to the endpoint to see if you can hit it. If you can, it may be something specific to the React Native implementation.
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 11, 2022, 7:26am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/6 "2022-05-11T07:26:05Z")
> [@Tyler](#):
>
> https://api-{app\_id}.sendbird.com
I’ve tested the api ( `https://api-{app_id}.sendbird.com`) from the browser and it’s working fine
---
### Author:  [@Tyler](https://community.sendbird.com/u/Tyler)
#### Post date: [May 11, 2022, 7:27am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/7 "2022-05-11T07:27:55Z")
This would mean that it’s likely an issue where the implementation is preventing the SDK from reaching out. We can try and reproduce it locally if you provide the version of Android, React Native and the SDK you’re using however we’ve not had any similar reports of this occurring and thus it is likely localized.
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 11, 2022, 7:45am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/8 "2022-05-11T07:45:47Z")
I’ve tested in different android versions from (8 to 11) and the same issue persists, as for RN version it’s 0.66.4 and chat SDK is: 3.1.7
---
### Author:  [@Tyler](https://community.sendbird.com/u/Tyler)
#### Post date: [May 11, 2022, 7:56am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/9 "2022-05-11T07:56:47Z")
Is this always on the emulator or physical devices?
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 11, 2022, 8:30am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/10 "2022-05-11T08:30:05Z")
My tests are mainly on emulator, but I’ve validated that the issue is there when using a physical device
---
### Author:  [@walter.rodriguez](https://community.sendbird.com/u/walter.rodriguez)
#### Post date: [May 11, 2022, 12:51pm UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/11 "2022-05-11T12:51:41Z")
@moe This small and simple demo works for me. Can you please try if it works for you there?
> **[GitHub - warodri-sendbird/react-native-local-cache: Simple sample for...](https://github.com/warodri-sendbird/react-native-local-cache)**
>
> Simple sample for Sendbird Local Cache with React Native - GitHub - warodri-sendbird/react-native-local-cache: Simple sample for Sendbird Local Cache with React Native
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 11, 2022, 9:28pm UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/12 "2022-05-11T21:28:22Z")
I’ve done a deep dive investigation on this, after long hours of debugging i found out that the issue is in the initialization step of the sendbird object it self
```auto
const sendbird = new SendBird({ appId: Config.SENDBIRD_APP_ID });
```
were if I directly set the appId as a string and not used “react-native-config” environment variables ex:
```auto
const sendbird = new SendBird({ appId: 'FEESADF-34ER-G5GH-GV77-4C87451DE5E9' });
```
it works, I have no idea how this is happening, but I need to use env variables for app id, since we should have one for testing and another for production.
Can anyone maybe try to reproduce the issue? please refer to my sample code mentioned in the issue details
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 11, 2022, 9:56pm UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/13 "2022-05-11T21:56:43Z")
I can confirm that it was an issue with our android “react-native-config” setup, where it was initializing as undefined:
```auto
const sendbird = new SendBird({ appId: undefined });
```
which did not throw any error? maybe this requires more investigation into why no exception is thrown at this stage.
---
### Author:  [@Tyler](https://community.sendbird.com/u/Tyler)
#### Post date: [May 12, 2022, 1:25am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/14 "2022-05-12T01:25:43Z")
Hi @moe,
I think ultimately the dummy call failing is the exception we throw here though I can understand expecting it to throw an error being undefined. I’ll relay that feedback to our Engineering team.
---
### Author:  [@moe](https://community.sendbird.com/u/moe)
#### Post date: [May 12, 2022, 2:16am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/15 "2022-05-12T02:16:34Z")
The dummy call failing exception happens when we call sendbird.connect(), but the initialization of the sendbird object happens at an earlier stage prior to calling connect (ideally on app start) so those are two different flows which should have different error handling, this I beleive will ease debugging where would different issues be located.
Thanks for the support
---
### Author:  [@Tyler](https://community.sendbird.com/u/Tyler)
#### Post date: [May 12, 2022, 2:17am UTC](https://community.sendbird.com/t/sendbird-chat-sdk-not-working-on-android/4625/16 "2022-05-12T02:17:13Z")
Ah okay. I see what you are saying. I will definitely bring that back to our Engineering team for review.