I'm using a barcode scanner (LS2208 OPOS mode) in an application and every time I close it the scanner is disabled. It starts to work again when I reopen the app.
In my app there is no call to disabled it, so why is this happening? Is this normal ?
The same thing happens with the sample app in the POS for .NET SDK
That is normal behavior.
Calls such as Close or Release method(Release is exclusive device only), or application termination or abort, will disable the OPOS/POS for.NET device.
However, termination or abort of the application may not be disable depending on timing.
It is considered a bug in either OPOS/POS for.NET/application.
Related
Background
I have an iOS app which scans for BLE devices in the Background. It worked well until I updated to iOS12. This is what I have:
App is configured to run in Background (e.g. location & bluetooth-central keys in .plist)
App is supposed to run continuously in Background, scanning for Peripherals. This is not to be confused with Background Fetch, which is a different use case.
App does not connect to Peripherals. It only reads the advertisement packets.
App gets suspended after running for a few hours in the Background.
App resumes normal operation when brought to the Foreground
App operated properly in iOS 11. Problems started after updating to iOS 12.x
I placed log messages in the App Delegate methods. This last thing I see is the app entering Background State. I never see a call to applicationWillTerminate(), as it is only called when the app is in the Foreground.
I have seen other posts (e.g. iOS 12 terminates apps in the background for no reason) for similar behavior with the Location stack. Using the test app written by the author of the post, I verified the problem has been fixed in iOS 12 for Location Services. But the BLE problems persist.
Has anyone found a workaround for this problem?
thanks in advance.
I am working on push notification in my Windows Phone App and I am having this issues.
From time to time the BackgroundTask which is responsible for push notification handling isn't wake up I know it- cause I've spread logs after each code line in my Task.
I know for sure that my token is valid and I am getting the notifications from the server.
This happens only when debugger is not attached.
I don't see any exception either in my log.
I can see in my logs, that one line before I am showing the Toast is cut at the end in a middle of writing (guess the task was terminated suddenly?)
Any ideas what can cause this behavior?
I think that the main problem was that I tried to use too many of CPU time , while writing logs and using my heavy application services (MvvmCross) such as Sqlite.
After removing logs, and heavy consuming time operations - everything worked :)
I would like to debug code in PreProduction environment but I'm wondering if it will bother other users who are using same AX client. Will it affect others if I debug code?
It should not bother other users since the debugger is a program separate to the client.
Add breakpoints to the code using F9, or selecting Toggle breakpoint in the debug menu or clicking on the gray line next to the code. The breakpoint is then user specific and the client will only stop and start debugging for your user.
If you set a breakpoint in your X++ code by using the breakpoint statement, that will bother users and when their actions reach the breakpoint statement, the client will stop and start a debugging session.
So use this:
And not this:
It will most likely not disrupt users in the way you think it may. Like Jan said, their clients could hang, but when your client is frozen during debugging, their clients will not be frozen at the same time, merely because you are debugging. They open their own sessions and connect to the AOS independently of each other. They would be affected by locked transactions, that should take seconds, but since you've potentially paused code execution in the middle of a transaction, it will maintain a lock.
You can demonstrate this by debugging in a development environment, then opening a second client instance on the same local or on a remote machine, and you will see that you can continue working/testing. This is what you should do if you are very concerned about impact.
If they have administrative or AX debugger permissions on the machine, global breakpoints turned on, and the debugger installed in tandem with the client where they are working, then technically they could launch a debugger session...but the planets sort of have to align for that to happen in most installations. It would be very bad practice for that to happen.
Is it possible to detect in Flex application browser window close event so that an action can be
started when user closes Flex application, does anyone know how to do that if it's possible in the
first place? The reason why i am asking this is because i have a multiuser Flex application where
every user has it's own directory on a server side. Application has logout button which triggers
cleanup of user's directory but what if the user just closes the window? I would like to be able
to lunch that same cleanup upon browser close window
In the page hosting your app, write a Javascript function triggered by window.onbeforeunload, and this function can call a function inside your Flex application.
Note that the onbeforeunload function is not guaranteed to work for all browsers.
I would not recommend that approach because the closing action fails too often, meaning worthless. My browser freezes and force-quitted several times a day. My computer sometimes freezes. My internet connection sometimes dies. I think, some browsers even do not guarantee those kinds of actions executed every time.
So, the session timeout might be one safe way in most cases.
You can also try having a socket connection, so that your server can ping if a user is alive and also can detect if socket is closed. Even socket, however, can be unresponsive or can be disconnected sometimes while user is still using the application.
You might want to be strategic.
i need to know how the Mac OS closes the running application when shutdown is pressed,
i am working in flex and want to capture that event (if that is an event or else) to stop closing my app state away.
i need my app to ask for close the app YES or NO. on yes resumes the shutdown and on no do not close the app and shutdown processes it also stopped.
need help
regards.
I'm not sure of anything Mac specific.
But can you add an event listener on the WindowedApplication for the close event? Also look at the closing event to do something before the app window closes.
I assume closing the main app window is the same as exiting the application.