I am new to Android. I want to develop a Android app which sends push notifications on Android devices. I have code that imports packages like "com.google.android.gms.common" but I am unable to import these packages. Get confused about Google cloud messaging. Which packages shall I use to develop push notification app.
I'm assuming you mean you want to send push notifications to Android devices.
When using GCM on Android you want to use the gradle dependency:
com.google.android.gms:play-services-gcm:8.3.0
Here is a simple project that only implements GCM.
Related
I'm developing Mobile App for IOS and Android and using the Expo platform during development. In this way, simply with a QR code, I can test the application in seconds for both devices Android and IOS.
I'm going to implement OneSignal Push notification for my React-Native Expo project, But before doing that I want to be sure that I can keep using "expo start" command and develop applications easily instead of building on Android Studio or XCode.
Is it possible to test OneSignal push notification with Expo?
It should work. I have used Google Firebase for expo notification which worked fine in devlopment.
I didn't work with One Signal. But according to their docs it should work with expo. Check out more here
Found the Answer deep inside of https://docs.expo.io/introduction/why-not-expo/
Just looking for clarification about how react-native apps are intended to be deployed to a platform's native app store (as opposed to being downloaded 2nd-hand from the Expo app) from a continuous-workflow perspective (as opposed to the mechanics of it).
Looking at the expo docs for standalone apps, it seems like the way a project would be continually (re)published would be to rebuild the app into the target platform and upload to the native platform's app store. Have not used react-native in some time, but I had initially thought that if you wanted to publish the app on a native platform's app store, you needed to eject the app and publish the platform's version of the ejected expo app to the native app store (and from then on, work on the app from the ejected version).
Could anyone with actual experience continually deploying react-native apps to native app stores enlighten me how what the standard workflow is here?
Expo provides a method for generating .ipa (iOS) or .apk (Android) without ejecting. You simply run expo build:ios (or build:android) to generate the standalone bundle which can be uploaded to the Play Store or App Store.
It is also worth noting that Expo provides internal over the air updates meaning you only need to publish your application to the App or Play store once. After the initial install, you can deploy updates through expo publish. Then, as per the documentation:
Expo will check for updates automatically when your app is
launched and will try to fetch the latest published version. If a new
bundle is available, Expo will attempt to download it before launching
the experience.
I'm currently developing an app with Expo. I've used Expo's Facebook API for users to sign in and realized that if I want to detach I'd have to use the React Native Facebook SDK. I've heard from many people that you can't publish an expo app to the app store, however, the expo website seems to say otherwise. Should I keep developing in Expo or detach and replace any of the expo imports I have?
You can easily generate a .apk or .ipa file with Expo and then upload it to the corresponding store (I have done this multiple times).
From Expo's docs:
The purpose of this guide is to help you create standalone binaries of your Expo app for iOS and Android which can be submitted to the Apple App Store and Google Play Store.
You can find detailed instructions on how to generate the binary files you need in this link.
What your friends might mean with "You can't publish an Expo app to the app store" is the publish command associated with Expo OTA updates. They even have a section explaining how to publish OTA updates to your standalone app.
A handy mindset when dealing with Expo is to think that "publishing" means using Expo's CLI tools to generate an OTA update, while "building" refers to the act of generating a new binary standalone file.
If you still need help with deploying your app to the app store check Expo's distribution guide.
I want to integrate Paypal SDK into an android application that I’ve created with React Native. I have used sharafat/react-native-paypal which is forked from MattFoley/react-native-paypal (MattFoley’s package is not updated anymore). It works on emulator without a problem, but when I create an apk, the app won’t open.
We want either an easy solution to the error in our current application
I have been investigating in this feature for a long time. All I can find is a pure iOS native code that checks for the key "UIApplicationLaunchOptionsLocationKey" from the LaunchOptions, if it is found it calls the LocationManager to start it and keep on listening to the location updates.
You can find this code in this github:
https://github.com/voyage11/GettingLocationWhenSuspended
I need the same concept, but with a way to integrate it in Worklight, through cordova plugin or something. As I'm already creating the geofencing triggers using the hybrid Worklight APIs, I need to keep the geofencing alive even when the app is suspended/terminated and also if the phone is restarted.
Please I need you support urgently. Thanks
Worklight provides the ability to create Cordova plug-ins.
You could implementing your own native code then, mimicking that from the Xcode project you've found on GitHub.
Read more here: Adding native functionality to hybrid applications