Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3346982
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 18, 20262026-05-18T01:22:05+00:00 2026-05-18T01:22:05+00:00

OK, I got it to codesign (turns out you don’t need to see the

  • 0

OK, I got it to codesign (turns out you don’t need to see the code sign and embedded.mobileprovision in the build log anymore!) but I want to get rid of my “may not respond to” warnings. I cannot find the problem after looking at all the other posts about these warnings…

In the Welcome_backView.h:

 @interface Welcome_backView : UIView {
Welcome_backViewController *refParentViewController;

}


- (id)initWithParentViewController:(Welcome_backViewController *)parent;
- (void)setSubviewsToLandscape;
- (void)setSubviewsToPortrait;

In the Welcome_back.m,

  #import "Welcome_backView.h"
  #import "Welcome_backViewController.h"
  @interface Welcome_backView()
//

@end

@implementation Welcome_backView



 - (void)setSubviewsToPortrait{
//do great things
 }

 - (void)setSubviewsToLandscape{
    //do more great things
 }

Then this is from Welcome_backViewController.m:

#import "Welcome_backViewController.h"
#import "Welcome_backView.h"

@interface Welcome_backViewController()
-(void) arrangeViews;
@end

@implementation Welcome_backViewController

UIView *welcome_backView;

 - (id)init {

welcome_backView = [[Welcome_backView alloc] initWithParentViewController:self];
    self.view = welcome_backView;
}

-(void) arrangeViews {
//if one thing
    [welcome_backView setSubviewsToPortrait];
//if another thing
    [welcome_backView setSubviewsToLandscape];
}

And, like so many posters, I get the warnings “UIView” may not respond to “-setSubviewsToLandscape” (and to portrait…same warning). I have tried all the usual suspects — misspellings of the method, using the class instead of the instance, not importing the header or having forgotten to put the method declarations in the header.

Truth is, the code seems to work fine…

Can anyone see what I’ve done wrong (can I get rid of the warnings)?

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-18T01:22:05+00:00Added an answer on May 18, 2026 at 1:22 am

    The warning is saying “UIView may not respond…” because you’ve declared the welcome_backView ivar as a UIVIew instead of your subclass of it.

    UIView doesn’t have the methods setSubviewsToXXX–your subclass of it does.

    Change this:

    UIView *welcome_backView;
    

    to this:

    Welcome_backView *welcome_backView;
    

    It works even when declared as UIView because at run-time, the ivar does point to an instance of Welcome_backView which responds to the setSubviewsToXXX methods.

    Another thing that isn’t causing problems (yet) is the names of the methods. Method names starting with “set” are generally used for property setter methods and could later cause confusion.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

Got a real simple question but can't figure out the solution. Got following code.
i always got error: Code Sign error: A valid provisioning profile matching the application's
Got this ScopeExit class off code-project but it would not build on GCC 4.5.3.
Got a problem with my add function to my database. The following code hangs
i tried to compile by iphone app in xcode and i got this Code
Got this error today while trying to build a project with checkstyle. This works
Got this error while trying to get the variables out of a class. Using
Got two versions of a query. Neither does quite what I need.. Trying to
I have a weird issue. Codesign refuses to sign this big project I have,
Got a bug in some legacy code which communicates with a payment terminal. Just

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.