Closed thiendangvan closed 8 months ago
hi, @thiendangvan , we have fixed this bug yesterday, and the released version SDK will be released this evening, you can try it this evening or tomorrow morning.
hi, @thiendangvan , we have fixed this bug yesterday, and the released version SDK will be released this evening, you can try it this evening or tomorrow morning.
okay got it thanks thanks @wade-portkey . btw i wanna ask have you got this issue during development on Mac? The SDK shows a blank screen after calling the login method:
hi, @thiendangvan , we have fixed this bug yesterday, and the released version SDK will be released this evening, you can try it this evening or tomorrow morning.
okay got it thanks thanks @wade-portkey . btw i wanna ask have you got this issue during development on Mac. The SDK shows a blank screen after calling the login method:
We have not encountered this issue. I suspect it is caused by the same reason as the one above. I will release a new beta version that has fixed the above issue. You can try it, and if there are still problems, please tell us.
hi, @thiendangvan , we have fixed this bug yesterday, and the released version SDK will be released this evening, you can try it this evening or tomorrow morning.
okay got it thanks thanks @wade-portkey . btw i wanna ask have you got this issue during development on Mac. The SDK shows a blank screen after calling the login method:
We have not encountered this issue. I suspect it is caused by the same reason as the one above. I will release a new beta version that has fixed the above issue. You can try it, and if there are still problems, please tell us.
The new beta version is 2.0.0-beta.3
, you can try it.
The new beta version is
2.0.0-beta.3
, you can try it.
let me try
We have not encountered this issue. I suspect it is caused by the same reason as the one above. I will release a new beta version that has fixed the above issue. You can try it, and if there are still problems, please tell us.
hi @wade-portkey, I'm still getting the same issue after update the 2.0.0-beta.3. steps:
logs when I calling the login method:
DEV2FOD] [I] <MMKV.cpp:167::initialize> version v1.3.3, page size 16384, arch arm64-v8a
[DEV2FOD] [I] <MMKV.cpp:219::initializeMMKV> Apple Device: 0, version: 64, mlock enabled: 0
[DEV2FOD] [I] <MMKV.cpp:226::initializeMMKV> root dir:
/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv
[DEV2FOD] [I] <MMKV_OSX.cpp:99::setIsInBackground> g_isInBackground:0
[DEV2FOD] [I] <libMMKV.mm:116::+[MMKV initializeMMKV:logLevel:handler:]> appState:0
[DEV2FOD] [I] <MemoryFile.cpp:97::open> open fd[0x27],
/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk
[DEV2FOD] [I] <MemoryFile.cpp:202::mmap> mmap to address [0x1035a8000], oldPtr [0x0],
[/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk]
[DEV2FOD] [I] <MemoryFile_OSX.cpp:35::tryResetFileProtection> protection on
[/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk]
is (null)
[DEV2FOD] [I] <MemoryFile.cpp:97::open> open fd[0x28],
/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk.crc
[DEV2FOD] [I] <MemoryFile.cpp:202::mmap> mmap to address [0x1035cc000], oldPtr [0x0],
[/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk.crc]
[DEV2FOD] [I] <MemoryFile_OSX.cpp:35::tryResetFileProtection> protection on
[/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk.crc]
is (null)
[DEV2FOD] [I] <MMKV_IO.cpp:210::loadMetaInfoAndCheck> meta file [portkey-sdk] has flag [0]
[DEV2FOD] [I] <MMKV_IO.cpp:80::loadFromFile> loading [portkey-sdk] with 0 actual size, file size 16384,
InterProcess 0, meta info version:4
[DEV2FOD] [I] <MMKV_IO.cpp:129::loadFromFile> loaded [portkey-sdk] with 0 key-values
if u need more info abt my environments like node version, pod version, macOS version, ... pls tell me
We have not encountered this issue. I suspect it is caused by the same reason as the one above. I will release a new beta version that has fixed the above issue. You can try it, and if there are still problems, please tell us.
hi @wade-portkey, I'm still getting the same issue after update the 2.0.0-beta.3. steps:
- update SDK version to 2.0.0-beta.3
- npx expo prebuild --clean
- expo ios
- call the login method -> show a blank screen
logs when I calling the login method:
DEV2FOD] [I] <MMKV.cpp:167::initialize> version v1.3.3, page size 16384, arch arm64-v8a [DEV2FOD] [I] <MMKV.cpp:219::initializeMMKV> Apple Device: 0, version: 64, mlock enabled: 0 [DEV2FOD] [I] <MMKV.cpp:226::initializeMMKV> root dir: /Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv [DEV2FOD] [I] <MMKV_OSX.cpp:99::setIsInBackground> g_isInBackground:0 [DEV2FOD] [I] <libMMKV.mm:116::+[MMKV initializeMMKV:logLevel:handler:]> appState:0 [DEV2FOD] [I] <MemoryFile.cpp:97::open> open fd[0x27], /Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk [DEV2FOD] [I] <MemoryFile.cpp:202::mmap> mmap to address [0x1035a8000], oldPtr [0x0], [/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk] [DEV2FOD] [I] <MemoryFile_OSX.cpp:35::tryResetFileProtection> protection on [/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk] is (null) [DEV2FOD] [I] <MemoryFile.cpp:97::open> open fd[0x28], /Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk.crc [DEV2FOD] [I] <MemoryFile.cpp:202::mmap> mmap to address [0x1035cc000], oldPtr [0x0], [/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk.crc] [DEV2FOD] [I] <MemoryFile_OSX.cpp:35::tryResetFileProtection> protection on [/Users/thiendang201/Library/Developer/CoreSimulator/Devices/CB00D97A-070A-45CB-808E-4225AB7B4724/data/Containers/Data/Application/FA4B5ADF-7848-4218-8678-E793DCA986C6/Documents/mmkv/portkey-sdk.crc] is (null) [DEV2FOD] [I] <MMKV_IO.cpp:210::loadMetaInfoAndCheck> meta file [portkey-sdk] has flag [0] [DEV2FOD] [I] <MMKV_IO.cpp:80::loadFromFile> loading [portkey-sdk] with 0 actual size, file size 16384, InterProcess 0, meta info version:4 [DEV2FOD] [I] <MMKV_IO.cpp:129::loadFromFile> loaded [portkey-sdk] with 0 key-values
ok i know, i will attempt to reproduce this issue and resolve it.
hi, @thiendangvan , we have fixed this bug yesterday, and the released version SDK will be released this evening, you can try it this evening or tomorrow morning.
okay got it thanks thanks @wade-portkey . btw i wanna ask have you got this issue during development on Mac? The SDK shows a blank screen after calling the login method:
hi @thiendangvan , is this issue only present when screen recording? does this issue occur when not recording the screen? I want to confirm if this issue is related to screen recording.
hi @thiendangvan , is this issue only present when screen recording? does this issue occur when not recording the screen? I want to confirm if this issue is related to screen recording.
hi @wade-portkey, it is not related to screen recording. it happens on the IOS emulator only, android emulator work fine
hi @thiendangvan , is this issue only present when screen recording? does this issue occur when not recording the screen? I want to confirm if this issue is related to screen recording.
hi @wade-portkey, it is not related to screen recording. it happens on the IOS emulator only, android emulator work fine
I didn't reproduce this issue here. Could you record the entire login flow so that I can try to find the reason.
hi @thiendangvan , is this issue only present when screen recording? does this issue occur when not recording the screen? I want to confirm if this issue is related to screen recording.
hi @wade-portkey, it is not related to screen recording. it happens on the IOS emulator only, android emulator work fine
I didn't reproduce this issue here. Could you record the entire login flow so that I can try to find the reason.
okay okay wait a sec
hi @wade-portkey, pls take a look: https://drive.google.com/file/d/1v__DUvHtGY9n7PmEQmPcaUE2AaMcOV8p/view?usp=sharing
@wade-portkey, may i ask if there are any updates for resolution in package.json? current resolutions:
"resolutions": {
"@invertase/react-native-apple-authentication": "^2.2.2",
"@portkey/react-native-sdk": "^2.0.0-beta.2",
"@react-native-async-storage/async-storage": "^1.17.6",
"@react-native-google-signin/google-signin": "^8.0.0",
"expo": "~49.0.15",
"expo-splash-screen": "~0.20.5",
"expo-status-bar": "~1.6.0",
"expo-system-ui": "~2.4.0",
"expo-device": "~5.4.0",
"expo-application": "~5.3.0",
"expo-auth-session": "5.2.0",
"expo-camera": "~13.4.4",
"expo-web-browser": "~12.3.2",
"expo-screen-capture": "~5.3.0",
"lottie-react-native": "^5.1.5",
"react": "~18.2.0",
"react-native": "~0.72.4",
"react-native-background-timer": "^2.4.1",
"react-native-config": "^1.4.6",
"react-native-fast-image": "^8.6.3",
"react-native-gesture-handler": "~2.12.0",
"react-native-get-random-values": "1.8.0",
"react-native-localize": "^2.2.1",
"react-native-mmkv": "^2.10.2",
"react-native-pager-view": "6.2.0",
"react-native-safe-area-context": "4.6.3",
"react-native-spinkit": "1.5.1",
"react-native-svg-uri": "^1.2.3",
"react-native-vector-icons": "^9.1.0",
"react-native-webview": "^13.6.0",
"react-native-svg": "13.9.0"
},
@wade-portkey, may i ask if there are any updates for resolution in package.json? current resolutions:
"resolutions": { "@invertase/react-native-apple-authentication": "^2.2.2", "@portkey/react-native-sdk": "^2.0.0-beta.2", "@react-native-async-storage/async-storage": "^1.17.6", "@react-native-google-signin/google-signin": "^8.0.0", "expo": "~49.0.15", "expo-splash-screen": "~0.20.5", "expo-status-bar": "~1.6.0", "expo-system-ui": "~2.4.0", "expo-device": "~5.4.0", "expo-application": "~5.3.0", "expo-auth-session": "5.2.0", "expo-camera": "~13.4.4", "expo-web-browser": "~12.3.2", "expo-screen-capture": "~5.3.0", "lottie-react-native": "^5.1.5", "react": "~18.2.0", "react-native": "~0.72.4", "react-native-background-timer": "^2.4.1", "react-native-config": "^1.4.6", "react-native-fast-image": "^8.6.3", "react-native-gesture-handler": "~2.12.0", "react-native-get-random-values": "1.8.0", "react-native-localize": "^2.2.1", "react-native-mmkv": "^2.10.2", "react-native-pager-view": "6.2.0", "react-native-safe-area-context": "4.6.3", "react-native-spinkit": "1.5.1", "react-native-svg-uri": "^1.2.3", "react-native-vector-icons": "^9.1.0", "react-native-webview": "^13.6.0", "react-native-svg": "13.9.0" },
I just updated to "@portkey/react-native-sdk": "^2.0.0-beta.3" and tried again but nothing change 😥
hi, @thiendangvan , we have fixed this bug yesterday, and the released version SDK will be released this evening, you can try it this evening or tomorrow morning.
okay got it thanks thanks @wade-portkey . btw i wanna ask have you got this issue during development on Mac? The SDK shows a blank screen after calling the login method:
I can not reproduce this issue today. may i ask, is it showing the blank screen every time you call the login method now? before this, it was able to show the right content, right? Have you tried uninstalling and reinstalling the app?
I can not reproduce this issue today. may i ask, is it showing the blank screen every time you call the login method now? before this, it was able to show the right content, right? Have you tried uninstalling and reinstalling the app?
hi @wade-portkey, yes it shows a blank screen every time I call the login method i think this issue is related to the expo-dev-client, u can see below video. before install the expo-dev-client i could see the login screen, but after i installed it i saw a blank screen:https://drive.google.com/file/d/1HVRMfrxURPyCqIMNlIMo6kTVq8OWsGL5/view?usp=sharing steps:
- npx expo install expo-dev-client
- npx expo prebuild
- yarn ios
I can not reproduce this issue today. may i ask, is it showing the blank screen every time you call the login method now? before this, it was able to show the right content, right? Have you tried uninstalling and reinstalling the app?
hi @wade-portkey, yes it shows a blank screen every time I call the login method i think this issue is related to the expo-dev-client, u can see below video. before install the expo-dev-client i could see the login screen, but after i installed it i saw a blank screen:https://drive.google.com/file/d/1HVRMfrxURPyCqIMNlIMo6kTVq8OWsGL5/view?usp=sharing steps:
- npx expo install expo-dev-client
- npx expo prebuild
- yarn ios
hi, @thiendangvan . Sorry for this. It seems that there was an error in our development documentation that misled you. You don't need to use expo-dev-client. You can try removing expo-dev-client and then rerunning the project to see if it works correctly on Android and iOS.
hi @wade-portkey, after removed the expo-dev-client it's work fine on both android & ios. but on ios the background is gray
get it, i will find the reason of the issue and solve it.
get it, i will find the reason of the issue and solve it.
thanks thanks
hi @wade-portkey, after removed the expo-dev-client it's work fine on both android & ios. but on ios the background is gray
hi, @thiendangvan , the reason for this issue is that we didn’t upload the iOS image resource files when publishing the npm package. The problem has been fixed now, and the new version is 2.0.1, you can try it.
hi, @thiendangvan , the reason for this issue is that we didn’t upload the iOS image resource files when publishing the npm package. The problem has been fixed now, and the new version is 2.0.1, you can try it.
i see, let me try. thanks @wade-portkey
thanks @wade-portkey. it's ok now. let me close this issue
Describe the bug I cannot finish the login flow. After I verify my email -> create a PIN code -> verify my face ID -> I will be redirected to the create PIN code screen
Necessary information package.json + yarn.lock files: https://drive.google.com/drive/folders/17xX2dR9_WNa56ws-Xvpa-zJmGO-M2q3p?usp=sharing
To Reproduce
Expected behavior should finish the login flow after verifying the face ID successfully
Screenshots https://drive.google.com/file/d/1II82cnbw45zlZUqYHWM7Gx5MQioozEsw/view?usp=sharing
Environment (please complete the following information):