expo

Failed authentication in Apple Developer Portal when execute expo build:ios

[亡魂溺海] 提交于 2021-02-07 21:27:32
问题 I'm trying to config automatically build iOS apps using Expo through Gitlab-CI . This are the commands that I am using: expo login -u expo_user -p expo_pass expo build:ios --non-interactive --apple-id my_id@domain.com --clear-dist-cert --clear-provisioning-profile --dist-p12-path "path_to_file.p12" --provisioning-profile-path "path_to_file.mobileprovision" I am already passing the respective values of this env vars: EXPO_APPLE_PASSWORD EXPO_IOS_DIST_P12_PASSWORD During the 2nd command

Network error with axios and android emulator

筅森魡賤 提交于 2021-02-07 11:48:45
问题 I got a React-Native application working with a NodeJS backend which serves an API. My React-Native front is using Expo and Axios to hit on a route of my NodeJS API (using Hapi, Joi, Knex), which will (for the example) update my DB (MySQL). Everything works properly with my iOS simulator. However, on Android Emulator, SOME of my hits on route ""does not work"" with the following error message : Network Error - node_modules/axios/lib/core/createError.js:16:24 in createError (actually, it

How can I do Signature Capture in React Native?

♀尐吖头ヾ 提交于 2021-02-07 07:23:40
问题 I'm trying to understand how I can do a signature capture in React Native. My App is created with create-react-native-app and Expo and I'd prefer to not have to eject the app to get this functionality to work. Would it be possible to wrap something like this in a webview? https://github.com/szimek/signature_pad I've also looked at this project, https://github.com/RepairShopr/react-native-signature-capture but it requires me to eject the app and use react-native link . Looking for any advice

Search engine in Expo

淺唱寂寞╮ 提交于 2021-02-05 08:10:42
问题 I follow this tutorial to add search to my Expo (React Native) app. After the last step I have this mistake:photo. What should I do? This is the part of the program. This is one of my navigation screens, where I have links for other screens: function InfoScreen({ navigation }) { return ( <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}> <Button title="Go back" onPress={() => navigation.goBack()} /> <View style={styles.container_new}> <Text style={styles.text}>Basic

Fast refresh in react native always fully reload the app

十年热恋 提交于 2021-02-04 08:36:41
问题 This question has been asked several times here(here the most relevant,Another example), but no solution has been proposed in any of them. So I have 2 questions to you guys: Any idea why it wouldn't work in a large project? I mean, there are any know issues with fast refresh related to the size of the project or the packages he includes that will make fast refresh stop working? There is any way to fix it? Is there a convenient way to edit an internal page in the app without using a fast

Xcode debug build vs release build

感情迁移 提交于 2021-02-02 09:15:07
问题 I am currently building a react native app using expo. However, I needed to use cocoapods, which is why I am now using Xcode. Since I have switched to Xcode, there has been a difference between my local debugging builds (that I run to a USB connected iPhone) vs the builds that get pushed to TestFlight. After doing some digging I have found that it may be due to the debug vs release schemes in Xcode. From what I've see it seems that the difference should really just be in performance, file

Xcode debug build vs release build

久未见 提交于 2021-02-02 09:10:59
问题 I am currently building a react native app using expo. However, I needed to use cocoapods, which is why I am now using Xcode. Since I have switched to Xcode, there has been a difference between my local debugging builds (that I run to a USB connected iPhone) vs the builds that get pushed to TestFlight. After doing some digging I have found that it may be due to the debug vs release schemes in Xcode. From what I've see it seems that the difference should really just be in performance, file

Xcode debug build vs release build

杀马特。学长 韩版系。学妹 提交于 2021-02-02 09:10:58
问题 I am currently building a react native app using expo. However, I needed to use cocoapods, which is why I am now using Xcode. Since I have switched to Xcode, there has been a difference between my local debugging builds (that I run to a USB connected iPhone) vs the builds that get pushed to TestFlight. After doing some digging I have found that it may be due to the debug vs release schemes in Xcode. From what I've see it seems that the difference should really just be in performance, file

Xcode debug build vs release build

故事扮演 提交于 2021-02-02 09:10:02
问题 I am currently building a react native app using expo. However, I needed to use cocoapods, which is why I am now using Xcode. Since I have switched to Xcode, there has been a difference between my local debugging builds (that I run to a USB connected iPhone) vs the builds that get pushed to TestFlight. After doing some digging I have found that it may be due to the debug vs release schemes in Xcode. From what I've see it seems that the difference should really just be in performance, file

图解 | 你管这破玩意儿叫TCP?

依然范特西╮ 提交于 2021-02-01 11:12:11
低并发编程,周一很颓废,周四很硬核 你是一台电脑,你的名字叫 A 经过 《如果让你来设计网络》 这篇文章中的一番折腾,只要你知道另一位伙伴 B 的 IP 地址,且你们之间的网络是通的,无论多远,你都可以将一个数据包发送给你的伙伴 B 这就是物理层、数据链路层、网络层这三层所做的事情。 站在第四层的你,就可以不要脸地利用下三层所做的铺垫,随心所欲地发送数据,而不必担心找不到对方了。 虽然你此时还什么都没干,但你还是给自己这一层起了个响亮的名字,叫做 传输层 。 你本以为自己所在的第四层万事大吉,啥事没有,但很快问题就接踵而至。 问题来了 前三层协议只能把数据包从一个主机搬到另外一台主机,但是,到了目的地以后,数据包具体交给哪个 程序 (进程)呢? 所以,你需要把通信的进程区分开来,于是就给每个进程分配一个数字编号,你给它起了一个响亮的名字: 端口号 。 然后你在要发送的数据包上,增加了传输层的头部, 源端口号 与 目标端口号 。 OK,这样你将原本主机到主机的通信,升级为了 进程和进程之间的通信 。 你没有意识到,你不知不觉实现了 UDP 协议 ! (当然 UDP 协议中不光有源端口和目标端口,还有数据包长度和校验值,我们暂且略过) 就这样,你用 UDP 协议无忧无虑地同 B 进行着通信,一直没发生什么问题。 但很快,你发现事情变得非常复杂...... 丢包问题 由于网络的不可靠