I have a Cloudwatch alarm set for the SWF workflow for a particular version. But as soon as I change the workflow version that particular alarm becomes useless.
Is there a way in cloudwatch to create an alarm on SWF workflow irrespective of the version?
Thank You,
Prasad
Related
I am new to react-native and implementing simple app where app will monitor the mobile's clock time and should set some flags so as to notify user to perform some task when he starts the app.
I want to continuously monitor mobile's clock time as a background job in the react native app such that, when user opens the app and if specific time has already passed, it should set some flag to take future decision.
After some research over blogs, I found that react-native-background-task and/or background-timers can be used. But I am finding difficulty in implementing it. Can anyone help me with the implementation example for the same.
Thank you in advance.
So, from your post I'm going to assume a few things. One being you'll develop on Android as well as iOS, you just want to use a plugin (not code a module yourself).
Unfortunately, unless I'm mistaken - there's no simple answer and I'll explain.
As Android and iOS go forward they are starting to limit usage of Apps in the background, specifically Android goes into 'Doze' mode and iOS works in a similar fashion.
For Android, you'll need to consider a few things and I'll concentrate on them, as you'll need to know this before actually creating a RN app.
Doze Mode
Starting from Android 6.0 (API level 23), Android introduces two
power-saving features that extend battery life for users by managing
how apps behave when a device is not connected to a power source. Doze
reduces battery consumption by deferring background CPU and network
activity for apps when the device is unused for long periods of time.
App Standby defers background network activity for apps with which the
user has not recently interacted.
While the device is in Doze, apps' access to certain battery-intensive
resources is deferred until maintenance windows. The specific
restrictions are listed in Power Management Restrictions.
Doze and App Standby manage the behavior of all apps running on
Android 6.0 or higher, regardless whether they are specifically
targeting API level 23. To ensure the best experience for users, test
your app in Doze and App Standby modes and make any necessary
adjustments to your code. The sections below provide details.
Cruically, you'll need to note:
The system does not allow sync adapters to run.
The system does not allow JobScheduler to run.
So firstly for android, you'll (probably) need to ensure your app is in a 'whitelist'. You can check the requirements of the list here:
https://developer.android.com/training/monitoring-device-state/doze-standby
Or, you can access the maintenance window with a plugin like here:
https://github.com/transistorsoft/react-native-background-fetch
Testing
Android give you some tools to do so, mainly running:
$ adb shell dumpsys battery unplug
$ adb shell am set-inactive <packageName> true
Headless JS
You can check out headless tasks, which could suit your situation:
https://facebook.github.io/react-native/docs/headless-js-android
Caveats:
Although Android state that the operating system itself acts like documented, devices themselves can have software built in which essentially kills background processes. Nokia is one of the worst. So be aware of this.
I am using Bolt-CMS in my project and every ten minutes Bolt logs me out from the CMS. Even if I am active and on the root account.
I know I use Bolt version 3.2.13
And that bolt runs on Silex. (with some Symfony components)
And I presume there is a config file for this.
So does anyone know where to find this config file or where I can turn the automatic logout off?
Thanks in advance!
First thing you should do is check the lifetime of your cookie (check the developer toolbar of your browser).
If this does not give a clue, then most likely there is a cron job that deletes your cookie files on the server. This question might be relevant in this scenario.
I understand how i can tie my application to the windows push notification service but the code i have to write to do so will only be reached when my app is started by the user. What if i want my application to receive push notifications when it has just been installed ?
the same question applies to background tasks
Setting up push notification channels and background tasks does require and app to be run at least once. You can, however, set up periodic notifications in Windows 8.1 through an entry in the manifest, so that you can have a live tile experience after install but before the app is run. If you do that, you can at least surface some info on the live tile right away to invite the user into the app, after which you can customize the experience much more with push notifications and background tasks.
You can find the periodic update URI field in the manifest editor's Application tab under Tile Update. The XML schema ref is here: http://msdn.microsoft.com/en-us/library/windows/apps/dn391689.aspx.
Who will install the background agent or create push notification channel in this case? Yes, it should.
I read about Worklight's Direct Update feature already. However, I still have some questions that would like to clarify:
Q1: Is it true that Apple allows Worklight Apps to be published to APP
Store even there is a direct update feature?
Q2: How will Apple review and monitor the Worklight Apps' content if
there is a huge change after the direct update? Or, Apple does not
worry about the cached web resource in the application, does it?
Q3: Is there any limitation or pre-condition about the direct update
for the web resource? For example, the major entries of html and js
script files must be existed... etc.
Q1: Is it true that Apple allows Worklight Apps to be published to APP Store even there is a direct update feature?
A1: There are existing Worklight customers that have submitted an application to the App Store and passed Apple's app submission process. For best results, make sure you use Worklight v5.0.6.1 or later.
Q2: How will Apple review and monitor the Worklight Apps' content if there is a huge change after the direct update? Or, Apple does not worry about the cached web resource in the application, does it?
A2: Apple only reviews app submissions to the App Store and whether or not they follow their guidelines. They do not review future updates to the application (as long as it was not re-submitted), for example in the form of a Direct Update unless there are some extra-ordinary circumstances (like inappropriate content that was discovered afterwards, for example...)
Q3: Is there any limitation or pre-condition about the direct update for the web resource? For example, the major entries of html and js script files must be existed... etc.
A3: I am not entirely sure I understand the question. There is no limitation in Direct Update - this feature replaces the existing web resources of an application with new ones. The only thing I can think of is that both the Worklight Studio (that the app was created on) and Worklight Server (that the app lives on) must be of the same version number.
An update.
Apple now allows code updates if you use a webview
3.3.2 An Application may not download or install executable code. Interpreted code may only be used in an Application if all scripts,
code and interpreters are packaged in the Application and not
downloaded. The only exception to the foregoing is scripts and code
downloaded and run by Apple's built- in WebKit framework, provided
that such scripts and code do not change the primary purpose of the
Application by providing features or functionality that are
inconsistent with the intended and advertised purpose of the
Application as submitted to the App Store.
Is there any way to make resource forks uncopyable? In particular I'm setting a custom badge icon to the files contained in a specific directory through NSWorkspace via – setIcon:forFile:options: and I'd like those badges to be lost as soon as the files gets copied outside the folder.
AFAIK there is no easy/standard way to make that happen...
IF the filesystems we are talking about are based locally on the the Mac itself then you can achieve what you want by implementing a daemon (running with high priviliges). This daemon basically integrates itself into the OS (via both FSEvent and kqueue) - this way it can monitor any file activity and act accordingly (remove the badge or similar).
For some source on how to build such a mechanism you can check this and this and this too.
IF you want to achieve this server-side there are several mechanisms - but they solely depend on the server technology (an notification and/or hooking mechanism).