I've completed a tracking system project in my blackberry 8520.
After I deploy my app to my mobile the application should start automatically and I should be able to switch to that application whenever I want.
When the application is in the background it should not terminate when I press the back button. Instead it should again go to background. It should close only when clicking the close option in the menu.
Are these possible? If yes please tell me how.
Go to your project Folder in eclipse.
Then open BlackBerry_App_Descriptor.xml
and then check the Auto-run on startup and save it.
This will run the application when you restart the phone.
Related
So we have a task that app1 needs to copy some data to clibboard then open app2 which reads this data from clipboad and uses it. This is already implemented and works. But the first time app1 need to access app2 iOS wanted me confirm that action with the following dialog: "app1 wants to open app2" with options to Open or Cancel. I pressed Open and now it never shows this dialog. However we need this dialog because we want to thorougly test this process, including the case when user presses Cancel. Is there any way to bring this dialog back without wiping our iphones?
We have tried:
Reinstalling both app1 and app2
Restarting device
Enabling and disabling developer mode (ios 16)
Enabling and disabling lockdown mode (ios 16)
Changing system time forward
None of these actions made this dialog to appear again. Wiping and reactivating and iphone will work of course but maybe there is a faster way?
Try deleting "app1" before re-installing it. When you just install a new app over the old one, the data associated with the old one remains in place. Deleting the app first should remove it and hopefully remove the permission to launch "app2" in the process.
Try the following:
Open the iPhone Settings app
Select "General"
Select "Transfer or Reset iPhone"
Select "Reset"
Select "Reset Location & Privacy"
If that doesn't work, select "Reset All Settings"
I made a very simple application using Automator to "Get Specified URLs". I saved it as an application on my desktop, but whenever I click on the icon to open the application, it does not run. No dialogs or errors were returned. I am using High Sierra, which is the OS my computer was shipped with (no recent updates) What might be the reason behind this?
In order to make the URLs open upon launching of the app, you will need to add the "Display Webpages" action to display the webpages you have chosen.
There are many ways to start application from another application in Android.
Is it possible to start application from another application in iOS? If possible, how do I do it?
Yes, it is possible in iOS if provided the app has its URL Scheme set. If you want to open your app from any other your app you can set the custom URL Scheme in info tab of project settings.
To test, run your app, minimize and then open safari and type the URL you just set, hit GO and your app will open.
Can you access the iPad Device settings using the UIAutomation instrument?
I can use deactivateAppForDuration, but that does not allow me to exit the app navigate to the settings page, change a setting, and navigate back to the app and move on.
any suggestion?
No, you cannot automate anything outside of the target application as of right now. When your app leaves the foreground the automation tool loses control until it returns (if it does at least).
I'm using PhoneGap in Xcode. The problem is that I want to quit application when user clicks on Logout button. How can this be achieved?
Is there any alertnative that objective-c code can be used to quit application?
You don't have to launch open using NSTask... open just calls into Launch Services, some of whose functionality is directly available from NSWorkspace.
To quit, you just call [[NSApplication sharedApplication] terminate:nil]. See NSApplication documentation.
You're technically not supposed to exit the application if you're planning to submit your App to the App Store.
See here: https://developer.apple.com/library/ios/#qa/qa2008/qa1561.html
Perhaps, you should bring the user back to some sort of login/landing page instead.