Plugin used: awesome_notification
This is my code for creating the local notification.
It is working fine up to android version 11, but after 12 version both the basic and schedule channel notification is not working.
Related
We have recently updated our react-native project to 0.62.2. To perform the linking we need to update the realm version to 6.0.0. It is working fine on ios but it is crashing on android 10 only. Below android 10 it is also working fine. We have realm version 0f 0.29.2 initially. After that we again degraded the version of realm to 0.29.2 then it is working fine. We have also updated the version above 6 also but the same problem occurs.
How can we update our realm to 6.0.0 or any version above it for android 10?
I have created Ionic 4 application and integrated Razorpay. Razorpay callback is working fine in android version 7.1 or greater version. but when I using Razorpay in android version 7.0.0 frame opens but when i clicked on Success or Failure then it reload my whole application and not calling any callback.
I'm using Expo.io for publishing my over-the-air updates. I have submitted several new official updates (so new SDK/IPA files) to the App and Play store. I'm still using the same version of Expo as before. Will my over the air updates go out to the previous versions(people haven't gotten the offical app/play store update)? Or are the old versions stuck until the user manually updates to the latest version so that they can get OTA updates again?
If you upload a new build to the app store and play store, the user will need to download the build in order to get OTA updates for that build.
If you just build and push to the expo server, the user will be able to get OTA updates without any download.
The standalone app knows to look for updates at your app's published url.
From the documentation : Publishing Guide
When you build the binary, the current version of your app JavaScript
is bundled so that it loads immediately the first time the app opens.
But you’re not stuck with that version of your code, you can publish
updates at any time after that without needing to re-build the binary.
For example, if you find a bug or want to add some functionality to
the app after submitting the binary.
The standalone app knows to look for updates at your app’s published
url, and if you publish an update then the next time a user opens your
app they will automatically download the new version. These are
commonly referred to as “Over the Air” (OTA) updates, the
functionality is similar to CodePush, but it is built into Expo so you
don’t need to install anything.
Core expo team member #ide answered your question in this comment:
The way Expo, the publishing system, and versions work is this:
The Expo client and standalone apps support multiple SDK versions (ex: 18, 17, 16, 15).
When you publish your project, the Expo server saves your project bundle and the "sdkVersion" value in exp.json or app.json.
When the Expo client loads your project, the server sends back the latest bundle with the greatest SDK version that your client supports. So if your client supports SDKs 15 through 18 and you've published your project with SDK 15 and SDK 16, the server will send back the latest bundle for SDK 16.
So if you had published your project with SDK 16 before but then went back to SDK 15, any client that supports SDK 16 would still receive the old SDK 16 bundle.
The old Play Store versions will still get OTA (exp publish) updates as long as the published URL hasn't changed, which you can set in your app.json. This is because that URL is hardcoded into the native code (it's in MainActivity.java for Android).
Your published URL will be expo.io/#your-username/slug. From app.json's documentation:
slug
Required. The friendly url name for publishing. eg: expo.io/#your-username/slug.
I'm moving to a new machine and want to start out fresh. I'm leaving Appcelerator Studio behind and want to go all CLI.
The project I'm working on is still on SDK 5.5.1.
When I try to build our app for the iPhone simulator it builds fine and launches the simulator but when it tries to start the app the simulator goes black execpt for the status bar. No errors are thrown in the terminal and nothing interesting shows up in console.app
I can launch the app in the simulator on my old machine without issues (done it 1000 times or so).
I build with: appc run -p ios
This is the last output I get:
[INFO] Launching iOS Simulator
-- Start simulator log -------------------------------------------------------
[INFO] Application started
[INFO] OurAppName/2.8.1 (5.5.1.b18727f)
This is my setup:
Appcelerator Command-Line Interface, version 5.5.1
2017-02-08 14:54:46
Name = Mac OS X
Xcode 8.1
Version = 10.12.3
Node.js Version = 4.7.3
npm Version = 2.15.11
Titanium CLI Version = 5.0.9
Titanium SDK Version = 5.5.1.GA
SDK Path = /Users/-/Library/Application Support/Titanium/mobilesdk/osx/5.5.1.GA
Target Platform = iphone
What am I missing?
You could try building on a specific simulator
run
appc run -p iOS --device-id
it will prompt you with all the devices available and you can choose among the list (choose an iOS 9 simulator, it looks like the problem is with the iOS 10 simulator)
Not sure if it helps, but we're using Titanium SDK 5.4.0, and so far still using Xcode 7. For another project, using Titanium 6 we are using Xcode 8.
We experienced some issues in communication between Studio/CLI and Xcode/Simulator.
if you are using Xcode 8.1 then you can use the following command
appc ti build -p ios -I 10.1
where -p is platform and -I is IOS version
if you want to check IOS version
Step 1: Go to Xcode
Step 2: Window -> Devices.
please see the image it will clear all things.
It worked for me.
i recently converted my mfp studio project to mfp cli cordova project.
when i preview my project everything work fine except "WLResourceRequest is not defined" that log to the console.
enter image description here
i noticed that the web preview works fine, but the mobile browser simulator not working and logs the same error
Same problem. I have a ionic project. This was working till I installed MFP 8.0 beta
Post that I m unable to make any adapter calls.
It doesn`t work in Chrome, but it works on my device. Using MFP 8.0