I want to disable buttons in the UIAction sheet and enable them after a certain condition is true. How do I achieve this? Any ideas?
-
4I know it's hard to change somebody's mind, but are you sure you really want to do this that way? Maybe instead you want to just show the action sheet without the buttons that are disabled, and when some condition is true, show the other instead (hiding the other if necessary) – Ed Marty Apr 13 '09 at 13:47
-
See an alternate answer I aggregates from numerous sources in this [SO answer](http://stackoverflow.com/a/9380142/100017) – Reuven Feb 21 '12 at 15:26
7 Answers
I found that craig's answer didn't work for me (on OS 3.1). After a little digging around I discovered that the subviews of UIActionSheet
are actually of an undocumented class UIThreePartButton
Anyway, this works for me (implemented as part of the UIActionSheetDelegete
method)
- (void)willPresentActionSheet:(UIActionSheet *)actionSheet // before animation and showing view
{
for (UIView* view in [actionSheet subviews])
{
if ([[[view class] description] isEqualToString:@"UIThreePartButton"])
{
if ([view respondsToSelector:@selector(title)])
{
NSString* title = [view performSelector:@selector(title)];
if ([title isEqualToString:@"Button 1"] && [view respondsToSelector:@selector(setEnabled:)])
{
[view performSelector:@selector(setEnabled:) withObject:NO];
}
}
}
}
}
Hope that helps someone else, although I'd echo Ed Marty's question of whether you'd be better off just omitting these buttons from the action sheet altogether instead of doing this. As always when using undocumented features, there is a risk of app store rejection, although this code is written to fail gracefully if Apple do chnage the APIs again in a future OS release.

- 3,241
- 3
- 25
- 20
-
6Never use `description` for comparing classes. Correct way is to use use `[view isKindOfClass:NSClassFromString(@"UIThreePartButton")];` – Kornel Dec 17 '09 at 14:10
-
4Using undocumented classes like this is a sure way to get rejected when submitting to App Store. – PeyloW Dec 29 '09 at 20:42
Is there a circumstance that can change, while the action sheet is open, that could cause the button to become enabled? If not, I think the better approach is to alter the buttons that the sheet displays based on your condition.
Otherwise, the only way of handling this is to iterate through the sheet's subviews, like Craig said, and look for the UIButton
objects. I'd be careful about using the button's title, though, because the title could (and should!) be localized for different languages. So comparisons against the title aren't all that reliable. Since you didn't create the button, you don't really know what the tag
or action
of each button would be, either, so that's a bit difficult, too.
Presumably, the buttons will appear in the subviews
array in the order you specified them to the UIActionSheet
, but since this isn't documented, there's no guarantee that they will appear in that order, or that they will continue to appear in that order in future releases of the Cocoa Touch SDK. Because of that, I'd worry mainly about being rejected from the App Store for using undocumented functionality.

- 26,829
- 3
- 55
- 74
-
You wouldn't be rejected from the App Store for this procedure. There's always a chance that Apple will change the subview order, and your application might start acting strange, but it is not the type of 'undocumented funcionality' that they would prohibit from the store. – Craig Otis Apr 14 '09 at 15:54
-
2True, it's not the same thing as private API, but it is private in the sense that it's based on experiment, not documentation. I would very strongly recommend against it. I'm not confident that Apple wouldn't reject it -- the agreement gives them a free hand in rejecting apps for any reason. – Alex Apr 14 '09 at 18:53
UIActionSheet is not intended for customizing. It should display actual set of available options. It should not change button's availability while on top. Just remove unused buttons, or use custom view instead

- 626
- 4
- 7
This is probably a bit late. But, the way I figured out is create UIButton(s) and add them to UIActionSheet subview. Make certain these buttons are placed on top and completely cover the default UIActionSheet button(s) to replace. When the UIButton is placed over the default UIActionSheet button, its UIResponder takes precedence over UIActionSheet button UIResponder. So, doing so you can disable and enable those buttons however you'd like anywhere in you UIViewController logic. This may be an alternative to accessing private methods to the SDK (like above - UIThreePartButton) and apple might reject your app. I believe this follows the Apple guidelines.
i.e. Setup UIButtons in order to enable / disable after certain conditions occur.
// Instantiate once within a method
if (self.actionSheet==nil) {
UIActionSheet *as = [[UIActionSheet alloc]
initWithTitle:@""
delegate:self
cancelButtonTitle:@"Cancel"
destructiveButtonTitle:@"Load Data"
otherButtonTitles:@"Update Data",nil];
//[actionSheet showInView:self.view];
self.loadUIButton.frame = CGRectMake(24.0f,25.0f,275.f,46.0f);
[as addSubview: self.loadUIButton];
self.updateUIButton.frame = CGRectMake(24.0f,78.0f,275.f,46.0f);
[as addSubview: self.updateUIButton];
//[actionSheet addSubview: self.cancelUIButton];
//[as showFromToolbar: self.navigationController.toolbar];
self.actionSheet = as;
[as release];
}
[self.actionSheet showFromToolbar: self.navigationController.toolbar];
NOTE: This worked perfectly in a previous app I built.

- 56
- 4
If you add the view to the action sheet, the view wont receive any event. You need to the view to the superview of the action sheet.
See below how i've added an button with touch up event:
- (void)didPresentActionSheet:(UIActionSheet *)actionSheet{
CGRect rect = CGRectMake(0,0, 320, 480);
UIButton* anImage = [[UIButton alloc] init];
[anImage setTitle:@"GHello worl" forState:UIControlStateNormal];
[anImage setTitle:@"GHello worl dfasd" forState:UIControlStateHighlighted];
[anImage setTitle:@"GHello worl selected" forState:UIControlStateSelected];
//[anImage setBackgroundImage:[UIImage imageNamed:@"photo.png"] forState:UIControlStateNormal];
[anImage addTarget:self action:@selector(buttonClicked:) forControlEvents:UIControlEventTouchUpInside];
rect = CGRectMake(0,0, 320, 220);
anImage.frame =rect;
[actionSheet.superview addSubview:anImage];
[anImage release];
}

- 177
- 2
- 7
I faced a similar problem when I had an action sheet that changes based on some conditions. I omitted the choices that are not applicable from the action sheet altogether but in some cases I end up with an action sheet with just one choice. This seems a bit silly, since I could activate that choice immediate without displaying the sheet at all.
However, I also want users to learn that clicking a certain button on screen gives them a list of choices they can choose from. That's why I want to display the action sheet also in cases when it has just one choice. I thought about disabling the non-applicable choices instead of omitting them from the sheet but that didn't feel right, either.
My case is related to having a user-icon in a custom bottom bar and pressing it presents the following choices:
- if logged in
- My Profile
- Log out
- if not logged in
- Log in

- 441
- 5
- 19
You could try [actionSheet valueForKey:@"_buttons"] in your UIActionSheetDelegate like so:
- (void)willPresentActionSheet:(UIActionSheet *)actionSheet
{
for (UIButton *btn in [actionSheet valueForKey:@"_buttons"])
{
[btn setBackgroundImage:[UIImage imageNamed:@"btnActionSheetUp.png"] forState:UIControlStateNormal];
[btn setBackgroundImage:[UIImage imageNamed:@"btnActionSheetDown.png"] forState:UIControlStateHighlighted];
}
}
Hopefully this wont change in future releases of the sdk.

- 2,716
- 1
- 33
- 42
-
Is this going to be rejected? In case that you have a lot of buttons, UIActionSheet is going to set an scroll with the buttons, & then, this is not working, do you know how to solve it? Thank you! – Oscar Dec 14 '11 at 09:23