I guess this doesn't work for Free plan. I try "canvas" but still getting regular ChatGPT responses
@NativeNotifyКүн бұрын
Yeah, you have to be a paying user for this to work
@dreamsachiever2123 күн бұрын
this video just comforts me as an android user. so much bs on iOS. wtf
@YSl113 күн бұрын
Link URL is not working
@TJMcCarty3 күн бұрын
Which Link URL? I just tried the ones in the description and it worked for me
@miraycivan71163 күн бұрын
Hello, I'm using Expo for my React Native project, currently on version 51. I performed an OTA update without upgrading to version 52. However, the app is not functioning on devices that received the update. How can I perform the update without upgrading to version 52?
@NativeNotifyКүн бұрын
I would create a new build and submit the new build to override the OTA.
@Motivate_mindset24 күн бұрын
increase action n decrease your overacting it will be good ok
@alignacestore5 күн бұрын
i get this error on my vs code terminal, and it says something about new arhitecture, and bridgless mode, how to fix that
@gurkiratz9 күн бұрын
This was so good! Subscribed
@NativeNotify9 күн бұрын
Thank you for your kind words!
@verawat9 күн бұрын
Perfect
@tirumaleshae75159 күн бұрын
This video helped me thank you bro you got new subscriber
@NativeNotify9 күн бұрын
I appreciate the kind words, welcome to the channel!
@kulek-tutiny9 күн бұрын
Thanx a lot for this quick review. It is very helpful
@FreeAcademy-x9o10 күн бұрын
Your Video Quality is good but you are not geeting more views because of these problems. if you want I can fix your problems.
@MrBarbasLuis11 күн бұрын
Ajajajajajajaja its the BEST tutorial. I am really frustrated with this new API key acces ajajajajaja. Tks a lot.
@pallyweb13 күн бұрын
I regret learning react-native expo , They keep bringing unwanted updates which brings irresolvable error wherever there is new change. I am planning to rewrite my whole app in Flutter. at least we know what is going on.
@NativeNotify11 күн бұрын
I really feel like Expo 52 could be the last really major change. With Expo 52, they switched to follow standard JavaScript practices used by other frameworks like Next.js. It’s looking like all the frameworks are starting to standardize to build apps similar to how Expo 52 now has you build apps. But I understand the frustration
@Bit-Bender17 күн бұрын
Thank you for reviewing my package! I'm glad to add that the package is now GDPR compliant so you can use this package and then run a simple command to download the fonts to your project and then it will correctly link them in your app so they bundled and ready for production!
@snowsproam838419 күн бұрын
Hey man , I recently been using native notify with expo and im getting the error no valid aps-environment entitlement string found for application. Would you know how to go about it as most stuff online are mentioning xcode but im building using eas for expo push notifications.
@NativeNotify19 күн бұрын
Hi. There's new iOS documentation inside of your Native Notify app. Click on that documentation and follow the instructions. That error indicates you may have said "no" to questions related to push notifications when setting up iOS push notifications. When you run "eas build", always make sure to say "yes" to everything related to push notifications. If you have any other questions, you can click the ? icon at the top of your Native Notify dashboard screen to find our support email. Thanks for using Native Notify!
@NativeNotify19 күн бұрын
@superxd2728 comment: if some one is getting render error after like ex: ERROR Error: Exception in HostFunction: Unable to convert string to floating point value: "large" , it can be fixed by upgrading to sdk 52 and then you can try : to check for dependency warnings and expected versions in the console during the expo start process. Updating the dependencies to their correct versions (as suggested in the warnings) can resolve issues and ensure the app works with the latest SDK. it worked for me!
@superxd272820 күн бұрын
if some one is getting render error after like ex: ERROR Error: Exception in HostFunction: Unable to convert string to floating point value: "large" , it can be fixed by upgrading to sdk 52 and then you can try : to check for dependency warnings and expected versions in the console during the expo start process. Updating the dependencies to their correct versions (as suggested in the warnings) can resolve issues and ensure the app works with the latest SDK. it worked for me!
@totallyalien23 күн бұрын
can I update version on app.json with eas update ?
@NativeNotify11 күн бұрын
Yes, I think you can. But when users first download your app, it won't be the new version, it will be whatever build you submitted. The user has to kill the app one or two times before the new version shows for eas update. If I'm remembering correctly.
@davidvalencia625624 күн бұрын
In Windows use wsl or git bash and it works
@darthnegativehunter865924 күн бұрын
dude explains why use typescript to javascript users. c++ user wonders why is this new to them
@faisalshaikh799425 күн бұрын
The new expo-video in SDK 52 is truly a game-changer, offering so many features right out of the box. I just want to know how I can enable the quality selection feature for HLS videos?
@alanhcrdz25 күн бұрын
Thank you for your video! I'm trying to debug my App in real time but it's not working, instead I get this error on android device and emulator: › Reloading apps No apps connected. Sending "reload" to all React Native apps failed. Make sure your app is running in the simulator or on a phone connected via USB. scanning works fine, but cannot debug in real time, cannot reload and make changes.
@ajaviles1325 күн бұрын
Wonderful video! I just installed my first development build because of you. And wow, this is AMAZING. Do you know how to change the app icon image? I am using my IOS iPhone.
@NativeNotify24 күн бұрын
In your assets folder there is an icon.png, I believe. You can change that to update the icon image in iOS
@ajaviles1324 күн бұрын
@@NativeNotify Got figured it out. I had an "iOS" folder that was overriding the app icon in my "app.json" file so I just deleted the "iOS" folder.
@verawat25 күн бұрын
First comment from THAILAND. Thank for your tutorial how to update Expo 51 to Expo 52
@lucasmolina5926 күн бұрын
I'm having issues with expo-notifications with this new version of expo. Problems with certain local notification functions not working as they should.
@NativeNotify26 күн бұрын
I’m coming out with a video on how to try to upgrade without breaking your app tomorrow. But in the end, it may make the most sense to create a new expo app from scratch so that you know everything with work, then copy your current app code into the new app. I definitely know expo-notifications work in 52 if you create a new app from scratch.
@lucasmolina5926 күн бұрын
@@NativeNotify
@lucasmolina5926 күн бұрын
@@NativeNotify Ok, although I have already tried with a new project with the new version and installing expo-notifications, and it still doesn't work as it should. Specifically in the trigger property of the object that is passed to the scheduleNotificationAsync method, where I assign the time but it is displayed immediately instead of the assigned time. Thanks anyway, and I'll wait for the video to watch it. Maybe it's my mistake.
@buttyline274126 күн бұрын
crying on how to come back to 51
@supremebeme26 күн бұрын
i've been trying to trigger notifications using supabase and edge functions lol
@jakeruth460327 күн бұрын
As a rule of thumb I wait at least a month or two to upgrade expo versions at this point lol. Just not worth it. I'd rather wait till everything is figured out.
@Ro_dolfoSilva27 күн бұрын
I’m getting some flicks in screens with Fla(t|sh)List on iOS. It’s very annoying. Also the need version warn about the UIRrfreshControl. 😢
@jamesdenmark139627 күн бұрын
Dont listen to those beginners, I never wrote a single line of react-native, and while I started the 52 sdk came, I was using the bottomsheet, I upgraded, had some issues, fixed it, and now running the latest version of expo, no problem what so ever.
@terjeoseberg99028 күн бұрын
I have been developing my app on my laptop and running it on my devices and on friend’s devices using debug mode where all the console log output shows up on my laptop. I now want to create a release candidate that’s uploaded to to my Expo account so that people can test it without involving my laptop. I’m having trouble finding a tutorial that explains how to accomplish this. Have you already created a tutorial for this? Are you willing to create one? Basically I’m not ready to release my app to the App Store, and I’d like to continue adding features and debugging my own local copy without changing the copy that my testers are using.
@jimmyjam7728 күн бұрын
Running this command builds an ipa on my computer, but how do I install it on my iPhone? There is no QR code. eas build --local --platform=ios --profile=development
@NativeNotify28 күн бұрын
You have to upload the ipa file to your Apple developer account and then you can download it to TestFlight on your iPhone. Apple doesn’t let you install directly to an iPhone like Android does. With Android, you can make an APK and directly install to an Android phone
@jimmyjam7728 күн бұрын
I ran eas build --local --platform=ios --profile=development, but there was no QR code at the end. Just a link to the local build artifacts. How do I load it on my phone?
@NativeNotify28 күн бұрын
You have to upload the file to an Apple developer then use TestFlight to see it, I’m not sure if building locally lets you install the developer build to your phone directly. I haven’t tried it before. I know what I did in the video works though
@jervi_sir28 күн бұрын
I did compare between freshly installed expo 52, I noticed they just added in `app.json` this line ` "expo": { "newArchEnabled": true, ` and there was no babel.config.json, so i beleive if we do upgrade from older to this 52 version, we have to manually add these changes one thing to note, I had some warning for Reanimated, I believe it was due to babel.config.json is no longer being in use, or maybe m missing something
@HoomanAskari28 күн бұрын
I didn’t want to upgrade to 52, but the expo go app on my iPhone stopped working, with an error that there is version incompatibility 😢
@DhanujayaYapabandara-t8v28 күн бұрын
Did you solve this error?
@NativeNotify28 күн бұрын
I just made a video about how to create a development build. You could try that instead of Expo Go. I’m going to try out my broken upgraded app in a development build next week and put it in a video. Maybe it’s safe to upgrade if you use a development build instead of Expo Go. I don’t know yet. If you wanted to stay in skd51 or lower, development builds should still work (I think, at least).
@HoomanAskari28 күн бұрын
@@NativeNotifydev builds work as I tested. Expo go is mostly broken though the issues with tab icons, images etc remain in the dev build too. There is a lot to fix! My only issue with dev build is it takes a while every time I change something in the libs , which should be fine if that remains to be the only option for now! I look forward to your video!
@TheAyogi29 күн бұрын
When I send a notification, I want to leave a link to a website so that the user goes to the link when he presses it. Is such a thing possible?
@viKii399329 күн бұрын
as per you guide access token this could not work
@NativeNotify29 күн бұрын
I pinned a comment saying you actually need to use the JSON file downloaded to generate a temporary bearer token using the Python code I thought you could skip. You DO need to run the Python code to get the bearer token
@egedovoevewero29 күн бұрын
Can’t test app using expo go on my iOS device. After using sdk52
@NativeNotify29 күн бұрын
Did you upgrade to 52 or is this a new app? And does the app work as a development build? I’m wondering if the issues just happen in Expo Go but maybe the app works as a development build after an upgrade. I’m probably going to test this out next week in a video.
@zenitsu413929 күн бұрын
@@NativeNotify the expo go app updated now only supports app in sdk52 version only
@NativeNotify29 күн бұрын
@@zenitsu4139 wow. I would say use development builds instead of Expo Go then for sdk51 or lower. I just made a video on how to do that. It's not too complicated.
@TheAyogiАй бұрын
kzbin.info/www/bejne/Z3ixqXxuntWFpa8 I did the steps here, everything works, but when I send it to others with the .apk extension, I don't get notifications?
@NativeNotifyАй бұрын
Follow the instructions in this video: kzbin.info/www/bejne/pWWldpqembGYqsUsi=VpcLm-mgfZt02kfm
@TheAyogi29 күн бұрын
@@NativeNotify When I send a notification, I want to leave a link to a website so that the user goes to the link when he presses it. Is such a thing possible?
@NativeNotify29 күн бұрын
@@TheAyogi You could maybe use a push data object in the push notification and then when the app opens, if you see the right push data object on the notification, have it redirect to a website in a in app web browser, or something like that. I don't know of a way to automatically have the user taken to a website after clicking on a notification.
@isaaccastillo8628Ай бұрын
Sentry with the SDK 52 have problems making development builds, I like Sentry, but it's not good lose that tool just for the upgrades.
@peterst6906Ай бұрын
Good job other than saying typescript is a subset of JavaScript. It's a superset, not a subset.
@matthieutsdАй бұрын
Trying to find any CLEAR documentation to setup X / Meta app events through expo / React Native during the last few dayss, but I feel like if I’m the first React Native developer to try it ever, I can’t find any simple tutorial, thank you for being honest
@MarlonEnglemamАй бұрын
just a few hours ago something changed and now when I try to run "npx expo start" with the SDK 51 I keep getting a prompt asking me to upgrade to SDK 52 and there seems not to be a way to bypass that, so now I'm stuck. Anyone else having this issue?
@NativeNotify28 күн бұрын
It looks like others are having this same issue. You may try creating a development build instead of using Expo Go. I just made a video about how to do that.
@brentvatneАй бұрын
hi there! can you create any issues for the examples you're having? for example, upgrading from sdk 51 to 52 should not result in any changes to fetch/axios behavior that would be any different from what you'd see in a new app. a minimal repro would be much appreciated! in general, the youtube comments that were cited are not actually very accurate. for example, expo install would not downgrade the version of the bottom-sheet library - it only upgrades packages that are part of the expo sdk. so that would have been a user error of some sort. nonetheless, thanks for covering the features!
@NativeNotifyАй бұрын
I had the native-notify package in SDK 51, then upgraded to SDK 52 and all the fetch/axios calls in that package broke, they didn't work. But when I created a new SDK 52 app, then installed native-notify, native-notify worked in a new SDK 52 app. I'm going to run some more tests soon though. I'm wondering if maybe the fetch calls just broke for Expo Go. I was testing in Expo Go after the upgrade. I'm going to see if the upgraded app will work in a development build soon and probably make a video about it.
@verawatАй бұрын
Agee with you.
@TSG-GOАй бұрын
Гавно эта версия
@carpyeАй бұрын
Agreed. A lot of things broke when I upgraded. It's a shame I can't use the new features (free performance gains are very attractive), but for now, if you already have the app you'll have to wait.
@A7MDMahmoudАй бұрын
thank you bro
@dhanishahamedc5382Ай бұрын
what if i am sending apk file manually to my users through email, will the app update automatically?
@pscardosoАй бұрын
If you are genereting the apk through of Expo, then yes.