I have created iPhone application with some Background fetching service process for data local notification purpose. Now the problem is I had logout my application then It's successfully gone from home screen to Login screen but still now I am receiving notification, I mean still running background services. I want to stop all the activities from my app after clicking the logout button.
My source within Logout button event method
- (void)logoutButtonClick:(id)sender
{
NSLog(#"Logout Clicked");
Login *loginview = [[Login alloc]init];
[self.navigationController pushViewController:loginview animated:YES];
}
If its NSTimer invalidate it on logout like [timer invalidate], if you already register local notifications then you can cancel them on logout like get all notifications [[UIApplication sharedApplication] cancelAllLocalNotifications].
Update: You post notification from logouButtonAction like this [[NSNotificationCenter defaultCenter] postNotificationName:#"ApplciaitonDidLoggedOut" object:nil];
Your onlogoutbutton method should be like this
- (void)logoutButtonClick:(id)sender
{
NSLog(#"Logout Clicked");
Login *loginview = [[Login alloc]init];
[self.navigationController pushViewController:loginview animated:YES];
[[NSNotificationCenter defaultCenter] postNotificationName:#"ApplciaitonDidLoggedOut" object:nil];
}
And in app delegate add observer for this notification in didFinishLaunch [[NSNotificationCenter defaultCenter ] addObserver:self selector:#selector(onLogut) name:#"ApplciaitonDidLoggedOut" object:nil];
and add method in appDelegate class
- (void) onLogut
{
//considering you have a timer property in app delegate,if not add one
[self.timer invalidate];
// if you want to cancel local notification
[[UIApplication sharedApplication] cancelAllLocalNotifications];
}
I try to reload a tableView from appDelegate
in AppDelegate.m, in the method who is in charge for Push Notification, "didReceiveRemoteNotification" i call a UIAlertView everytime when a notification arrives.
UIAlertView *alertView = [[UIAlertView alloc] initWithTitle:#"Notification received" message:[NSString stringWithFormat:#"%#", titleMsg] delegate:self cancelButtonTitle:#"OK" otherButtonTitles:nil, nil];
alertView.delegate = self;
[alertView show];
and when the user click "OK" button, should be a reading of database and reload the tableview
// Reload the table when the user click "OK" button in the alert
- (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex
{
if ([alertView.title isEqualToString:#"Notification received"])
{
if (buttonIndex == [alertView cancelButtonIndex])
{
// Stop the sound for notifications
[self stopSoundForNotifications];
// Refresh table messages
AccueilViewController * avc = [[AccueilViewController alloc] init];
[avc readMsgsFromDB];
[avc reloadTableMsgsReceived];
[[NSNotificationCenter defaultCenter] postNotificationName:#"ReadMessagesFromDB" object:nil];
[[NSNotificationCenter defaultCenter] postNotificationName:#"ReloadDataFromDelegate" object:nil];
}
}
}
In the header i added to the protocol UIAlertViewDelegate
Do you have some ideas? Thanks
You put the condition on cancel button instead of that put the condition on OK button
- (void)alertView:(UIAlertView *)alertView clickedButtonAtIndex:(NSInteger)buttonIndex
{
if ([alertView.title isEqualToString:#"Notification received"])
{
if (buttonIndex == [alertView OKButtonIndex])
{
// then fire notification
// Stop the sound for notifications
[self stopSoundForNotifications];
// Refresh table messages
AccueilViewController * avc = [[AccueilViewController alloc] init];
[avc readMsgsFromDB];
[avc reloadTableMsgsReceived];
[[NSNotificationCenter defaultCenter] postNotificationName:#"ReadMessagesFromDB" object:nil];
[[NSNotificationCenter defaultCenter] postNotificationName:#"ReloadDataFromDelegate" object:nil];
}
}
It looks like you are creating a new instance of AccueilViewController, rather than accessing an existing instance. So those readMsgsFromDB and reloadTableMsgsReceived are being processed by an instance which is not visible.
If you amend your AccueilViewController code, you can register to receive those notifications, and your existing instance can then act on them to reload the data. In fact, I would use only one notification, and combine the two method calls into one.
So delete the second postNotification, and in your AccueilViewController add the following to your viewDidLoad method:
[[NSNotificationCenter defaultCenter] addObserver:self selector:#selector(notificationReceived) name:#"ReadMessagesFromDB" sender:nil];
Then add a method to combine the two actions:
-(void)notificationReceived {
[self readMsgsFromDB];
[self reloadTableMsgsReceived];
}
So, when your AlertView button is pressed, the notification will be posted. The notificationReceived method in your existing AccueilViewController instance will fire, causing the messages to be read from the database and the table to be reloaded. You should also add a call to remove the view controller from the notification centre before it is deallocated:
[[NSNotificationCenter defaultCenter] removeObserver:self name:#"ReadMessagesFromDB" object:nil];
I have a UIAlertView which pops up with a message and a single button "Continue". What I would like for is that a Shake Gesture would also call the same code as hitting the continue button. However, I'm not sure if this is possible with the UIAlertView in iOS7 or if I have to create my own custom alert view.
I have tried implementing:
(void)motionEnded:(UIEventSubtype)motion withEvent:(UIEvent *)event { ... }
and
canBecomeFirstResponder { return YES; }
But while they work normally with the main view set to becomeFirstResponder they don't respond once the UIAlertView pops up. So then, I tried implementing these in a Category for UIAlertView+MotionResponder.h to try to extend UIAlertView, but the motionEnded is not getting called even though canBecomeFirstResponder is correctly returning YES.
So should this work? Or do I have to implement my own alert view?
According to the documentation
The UIAlertView class is intended to be used as-is and does not support subclassing. The view hierarchy for this class is private and must not be modified.
The internal view hierarchy of UIAlertView is much more complicated than it appears and starting from iOS 7 it is not even added to any UIWindow, so it's no big surprise that it doesn't participate to the responder chain as you expect.
However, you might consider of implementing the motion recognition logic within your controller instead and to have it triggering the UIAlertView dismissal.
You just need to keep a reference to the UIAlertView instance, detect the shake gesture in the controller and send a –dismissWithClickedButtonIndex:animated: message to the alert, in order to dismiss it.
EDIT
The above technique won't work when the UIAlertView is presented on top of the current controller since it will intercept the shake gesture and the controller method will never be called.
To make it work, you have to detect the gesture at a window level. Here's a brief example of how you can do.
First we define a category over UIWindow that intercepts the shake gesture and broadcasts a notification (I'll just post the #implementation, since the #interface is empty)
#implementation UIWindow (Shake)
- (void)motionEnded:(UIEventSubtype)motion withEvent:(UIEvent *)event {
if (event.type == UIEventTypeMotion && event.subtype == UIEventSubtypeMotionShake) {
[[NSNotificationCenter defaultCenter] postNotificationName:#"UIWindowDidShake" object:nil userInfo:nil];
}
}}
#end
then in the controller we register to the notification when showing the alert and we dismiss the alert when the notification arrives. Finally we can remove the controller from the observers as soon as the alert has been dismissed.
#property (nonatomic, strong) UIAlertView *alert;
...
- (IBAction)showAlert:(id)sender {
[[NSNotificationCenter defaultCenter] addObserver:self selector:#selector(dismissAlert) name:#"UIWindowDidShake" object:nil];
self.alert = [[UIAlertView alloc] initWithTitle:nil message:#"An alert" delegate:self cancelButtonTitle:#"Ok" otherButtonTitles:nil];
[self.alert show];
}
- (void)dismissAlert {
[self.alert dismissWithClickedButtonIndex:0 animated:YES];
}
- (void)alertView:(UIAlertView *)alertView didDismissWithButtonIndex:(NSInteger)buttonIndex {
[[NSNotificationCenter defaultCenter] removeObserver:self name:#"UIWindowDidShake" object:nil];
}
I am making an app that should support iOS versions from iOS5 onwards. It uses a UIAlertView, and if it's visible when the user presses the home button, I would like it to be dismissed before the user returns to the app (i.e. it's gone when the app is re-opened using multitasking). All methods in the app delegate show it as not visible (isVisible=NO) even if it is still visible when reopened. Is there a way to do this?
Thanks.
Or you inherit your class from UIAlertView and add NSNotification observer for UIApplicationWillResignActiveNotification and when notification occurs call to alertview method dismissWithClickedButtonIndex:
Example:
.h file
#import <UIKit/UIKit.h>
#interface ADAlertView : UIAlertView
#end
.m file
#import "ADAlertView.h"
#implementation ADAlertView
- (void) dealloc {
[[NSNotificationCenter defaultCenter] removeObserver:self];
}
- (id) initWithTitle:(NSString *)title
message:(NSString *)message
delegate:(id)delegate
cancelButtonTitle:(NSString *)cancelButtonTitle
otherButtonTitles:(NSString *)otherButtonTitles, ... {
self = [super initWithTitle:title
message:message
delegate:delegate
cancelButtonTitle:cancelButtonTitle
otherButtonTitles:otherButtonTitles, nil];
if (self) {
[[NSNotificationCenter defaultCenter] addObserver:self
selector:#selector(dismiss:)
name:UIApplicationDidEnterBackgroundNotification
object:nil];
}
return self;
}
- (void) dismiss:(NSNotification *)notication {
[self dismissWithClickedButtonIndex:[self cancelButtonIndex] animated:YES];
}
#end
With your own class inherited from UIAlertView you are need not to store link to alertview or something else, only one thing that you must do its replace UIAlertView to ADAlertView (or any other class name).
Feel free to use this code example (if you are not using ARC, you should add to the dealloc method [super dealloc] after [[NSNotificatioCenter defaultCenter] removeObserver:self])
Keep a reference to the displayed UIAlertView in your app delegate. When you show the alert, set the reference; when the alert is dismissed, nil out the reference.
In your app delegate's applicationWillResignActive: or applicationDidEnterBackground: method, call the dismissWithClickedButtonIndex:animated: method on the reference to the alert view. This would take care of dismissing it on pressing the "home" button.
Keep in mind that applicationWillResignActive: will be called for things such as phone calls, so you need to decide if you'd like to dismiss the alert in cases like that or if you should keep it up through the phone call.
Apple recommends dismissing any UIAlertViews/UIActionSheets when entering background state in iOS 4. This is to avoid any confusion on the user's part when he relaunches the application later. I wonder how I could elegantly dismiss all UIAlertViews at once, without retaining a reference to it everytime I set one up...
Any idea ?
My call would be to add a category to UIAlertview adding the following function :
- (void) hide {
[self dismissWithClickedButtonIndex:0 animated:YES];
}
And to suscribe to UIApplicationWillResignActiveNotification :
[[NSNotificationCenter defaultCenter] addObserver:alertView selector:#selector(hide) name:#"UIApplicationWillResignActiveNotification" object:nil];
I was intrigued by Dad's answer (funny username :), and curious why it was down-voted.
So I tried it.
Here is the .m part of a subclass of UIAlertView.
Edit: (Cédric) I have added a way to catch calls to delegate methods and remove the observer then to avoid multiple registrations to the notification center.
Everything bundled in a class in this github repo: https://github.com/sdarlington/WSLViewAutoDismiss
#import "UIAlertViewAutoDismiss.h"
#import <objc/runtime.h>
#interface UIAlertViewAutoDismiss () <UIAlertViewDelegate> {
id<UIAlertViewDelegate> __unsafe_unretained privateDelegate;
}
#end
#implementation UIAlertViewAutoDismiss
- (id)initWithTitle:(NSString *)title
message:(NSString *)message
delegate:(id)delegate
cancelButtonTitle:(NSString *)cancelButtonTitle
otherButtonTitles:(NSString *)otherButtonTitles, ...
{
self = [super initWithTitle:title
message:message
delegate:self
cancelButtonTitle:cancelButtonTitle
otherButtonTitles:nil, nil];
if (self) {
va_list args;
va_start(args, otherButtonTitles);
for (NSString *anOtherButtonTitle = otherButtonTitles; anOtherButtonTitle != nil; anOtherButtonTitle = va_arg(args, NSString *)) {
[self addButtonWithTitle:anOtherButtonTitle];
}
privateDelegate = delegate;
}
return self;
}
- (void)dealloc
{
privateDelegate = nil;
[[NSNotificationCenter defaultCenter] removeObserver:self name:UIApplicationDidEnterBackgroundNotification object:nil];
[super dealloc];
}
- (void)setDelegate:(id)delegate
{
privateDelegate = delegate;
}
- (id)delegate
{
return privateDelegate;
}
- (void)show
{
[[NSNotificationCenter defaultCenter] addObserver:self
selector:#selector(applicationDidEnterBackground:)
name:UIApplicationDidEnterBackgroundNotification
object:nil];
[super show];
}
- (void)applicationDidEnterBackground:(NSNotification *)notification
{
[super dismissWithClickedButtonIndex:[self cancelButtonIndex] animated:NO];
[[NSNotificationCenter defaultCenter] removeObserver:self name:UIApplicationDidEnterBackgroundNotification object:nil];
}
#pragma mark - UIAlertViewDelegate
// The code below avoids to re-implement all protocol methods to forward to the real delegate.
- (id)forwardingTargetForSelector:(SEL)aSelector
{
struct objc_method_description hasMethod = protocol_getMethodDescription(#protocol(UIAlertViewDelegate), aSelector, NO, YES);
if (hasMethod.name != NULL) {
// The method is that of the UIAlertViewDelegate.
if (aSelector == #selector(alertView:didDismissWithButtonIndex:) ||
aSelector == #selector(alertView:clickedButtonAtIndex:))
{
[[NSNotificationCenter defaultCenter] removeObserver:self
name:UIApplicationDidEnterBackgroundNotification
object:nil];
}
return privateDelegate;
}
else {
return [super forwardingTargetForSelector:aSelector];
}
}
#end
It works nicely.
It's great, because you can just start using it the same way that you used to use UIAlertView.
I haven't had time to test it thoroughly, but I didn't notice any side effect.
A totally different approach is a recursive search.
Recursive function for your application delegate
- (void)checkViews:(NSArray *)subviews {
Class AVClass = [UIAlertView class];
Class ASClass = [UIActionSheet class];
for (UIView * subview in subviews){
if ([subview isKindOfClass:AVClass]){
[(UIAlertView *)subview dismissWithClickedButtonIndex:[(UIAlertView *)subview cancelButtonIndex] animated:NO];
} else if ([subview isKindOfClass:ASClass]){
[(UIActionSheet *)subview dismissWithClickedButtonIndex:[(UIActionSheet *)subview cancelButtonIndex] animated:NO];
} else {
[self checkViews:subview.subviews];
}
}
}
Calling it from the applicationDidEnterBackground procedure
[self checkViews:application.windows];
huh. Haven't tried this yet, but I wonder if it would make sense to create a subclass of UIAlertView that listens for this Notification and closes itself if so...
That'd have the "automatically" without retaining / keeping it around characteristic OP is requesting. Make sure to unregister for the notification on close (else boom!)
As someone mentioned in a comment: the accepted answer isn't the best/cleanest one since iOS 4.0 when we have blocks! Here's how I do it:
UIAlertView* alert = [[UIAlertView alloc] initWithTitle:#"Alert!" message:#"This alert will dismiss when application resigns active!" delegate:self cancelButtonTitle:#"OK" otherButtonTitles:nil];
[alert show];
[[NSNotificationCenter defaultCenter] addObserverForName:UIApplicationWillResignActiveNotification object:nil queue:[NSOperationQueue mainQueue] usingBlock:^(NSNotification* notification){
[alert dismissWithClickedButtonIndex:0 animated:NO];
}];
UIAlertView was deprecated in iOS 8 in favor of the UIAlertController. Unfortunately, this proves to be a tricky problem because the accepted solution won't work, as Apple explicitly doesn't support subclassing UIAlertController:
The UIAlertController class is intended to be used as-is and does not support subclassing. The view hierarchy for this class is private and must not be modified.
My solution is to simply traverse the view controller tree and dismiss all UIAlertControllers that you find. You can enable this globally by creating an extension of UIApplication and then calling it in the AppDelegate applicationDidEnterBackground method.
Try this (in Swift):
extension UIApplication
{
class func dismissOpenAlerts(base: UIViewController? = UIApplication.sharedApplication().keyWindow?.rootViewController)
{
//If it's an alert, dismiss it
if let alertController = base as? UIAlertController
{
alertController.dismissViewControllerAnimated(false, completion: nil)
}
//Check all children
if base != nil
{
for controller in base!.childViewControllers
{
if let alertController = controller as? UIAlertController
{
alertController.dismissViewControllerAnimated(false, completion: nil)
}
}
}
//Traverse the view controller tree
if let nav = base as? UINavigationController
{
dismissOpenAlerts(nav.visibleViewController)
}
else if let tab = base as? UITabBarController, let selected = tab.selectedViewController
{
dismissOpenAlerts(selected)
}
else if let presented = base?.presentedViewController
{
dismissOpenAlerts(presented)
}
}
}
And then in your AppDelegate:
func applicationDidEnterBackground(application: UIApplication)
{
UIApplication.dismissOpenAlerts()
}
I Have had solved this with the following code:
/* taken from the post above (Cédric)*/
- (void)checkViews:(NSArray *)subviews {
Class AVClass = [UIAlertView class];
Class ASClass = [UIActionSheet class];
for (UIView * subview in subviews){
NSLog(#"Class %#", [subview class]);
if ([subview isKindOfClass:AVClass]){
[(UIAlertView *)subview dismissWithClickedButtonIndex:[(UIAlertView *)subview cancelButtonIndex] animated:NO];
} else if ([subview isKindOfClass:ASClass]){
[(UIActionSheet *)subview dismissWithClickedButtonIndex:[(UIActionSheet *)subview cancelButtonIndex] animated:NO];
} else {
[self checkViews:subview.subviews];
}
}
}
/*go to background delegate*/
- (void)applicationDidEnterBackground:(UIApplication *)application
{
for (UIWindow* window in [UIApplication sharedApplication].windows) {
NSArray* subviews = window.subviews;
[self checkViews:subviews];
}
}
The straightforward way is to hold a reference to the UIAlertView so you can dismiss it. Of course as petert mentioned you can do it with a Notification or use the delegate method on UIApplication
applicationWillResignActive:
does not always mean that you are going to the background. You will for example also receive that delegate call and notification (you get both) when the user gets a phone call or receives and SMS. So you have to decide what should happen if the user gets an SMS and presses cancel to stay in your app. You maybe want to make sure that your UIAlertView is still there.
So I would dismiss the UIAlertView and save the state in the delegate call when you really go into the background:
applicationDidEnterBackground:
Have a look at Session 105 - Adopting Multitasking on iOS4 of WWDC10 available for free at developer.apple.com. It gets interesting at 16:00 min
Check out this graphic to understand the different states of an application
I have this on my TODO list, but my first instinct would be to listen out for the notifcation UIApplicationWillResignActiveNotification (see UIApplication) in the views where you have things like UIAlertView - here you can programmatically remove the alert view with:
(void)dismissWithClickedButtonIndex:(NSInteger)buttonIndex animated:(BOOL)animated
The discussion for this method even suggests what it's for in iOS4!
In iPhone OS 4.0, you may want to call this method whenever your application moves to the background. An alert view is not dismissed automatically when an application moves to the background. This behavior differs from previous versions of the operating system, where they were canceled automatically when the application was terminated. Dismissing the alert view gives your application a chance to save changes or abort the operation and perform any necessary cleanup in case your application is terminated later.
if you only have one or two specific alert windows you show (as do most apps), then you can just create an assign ivar to the alert:
#property (nonatomic, assign) UIAlertView* alertview;
Then, in the app delegate:
[self.viewController.alertview dismissWithClickedButtonIndex:[self.viewController.alertview cancelButtonIndex] animated:NO];
You can put this in applicationDidEnterBackground: or wherever you see fit. It closes the alert programmatically upon application exit. I've been doing this and it works great.
Create category on UIAlert View
Use http://nshipster.com/method-swizzling/
Swizzle "show" method
Keep track of alert view shown by keeping week references in array.
-
When you want to remove all data call Dismiss on saved alert views and empty an array.
An alternative solution, based on plkEL's, answer, where the observer is removed when the app is put in the background. If user dismisses the alert by pressing a button, the observer will still be active, but only until the app is put in the background (where the block is run - with an "nil alertView" - and the observer removed).
UIAlertView *alert = [[UIAlertView alloc] initWithTitle:title
message:message
delegate:alertDelegate
cancelButtonTitle:cancelButtonText
otherButtonTitles:okButtonText, nil];
[alert show];
__weak UIAlertView *weakAlert = alert;
__block __weak id observer = [[NSNotificationCenter defaultCenter] addObserverForName:UIApplicationWillResignActiveNotification object:nil queue: [NSOperationQueue mainQueue] usingBlock:^(NSNotification* notification){
[weakAlert dismissWithClickedButtonIndex:[weakAlert cancelButtonIndex] animated:NO];
[[NSNotificationCenter defaultCenter] removeObserver:observer];
observer = nil;
}];