Yesterday I recognized a ton of warnings regarding the parse.com library: 
&gt; URGENT: all bitcode will be dropped because &#39;[path]/Parse.framework/Parse(PFAnalytics.o)&#39; was built without bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. Note: This will be an error in the future.

I am aware of the fact that I can remove those warning with [this answer](https://stackoverflow.com/a/30856364/2442804) but am now wondering if it will have any negative impact in regards to AppStore submission and / or actual performance of my app.

Xcode informs you regarding bitcode
&gt;Activating this setting indicates that the target or project should generate bitcode during compilation for platforms and architectures which support it.  For Archive builds, bitcode will be generated in the linked binary for submission to the app store.  For other builds, the compiler and linker will check whether the code complies with the requirements for bitcode generation, but will not generate actual bitcode. [ENABLE_BITCODE]

But I am not getting any really useful information out of this text.

- Can I use the linked answer to circumvent the issue without any negative impact and without compromising a future AppStore submission? 
- What does the `ENABLE_BITCODE` actually do, will it be a non-optional requirement in the future?
- Are there any performance impacts if I enable / disable it?

Impact of Xcode build options &quot;Enable bitcode&quot; Yes/No

I&#39;m still struggling with promises, but making some progress thanks to the community here.

I have a simple JS function which queries a Parse database. It&#39;s supposed to return the array of results, but obviously due to the asynchronous nature of the query (hence the promises), the function returns before the results, leaving me with an undefined array.

What do I need to do to make this function wait for the result of the promise?

Here&#39;s my code:

    function resultsByName(name)
    {   
        var Card = Parse.Object.extend(&quot;Card&quot;);
        var query = new Parse.Query(Card);
        query.equalTo(&quot;name&quot;, name.toString());
        
        var resultsArray = [];
        
        var promise = query.find({
                   success: function(results) {
                   // results is an array of Parse.Object.
                                 console.log(results);
                                 //resultsArray = results;
                                 return results;
                   },
                   
                   error: function(error) {
                   // error is an instance of Parse.Error.
                                 console.log(&quot;Error&quot;);
                   }
        });                           
    
    }



How do I wait for a promise to finish before returning the variable of a function?

I have a `tableview`, where sometimes there might not be any results to list, so I **would like to put something up that says &quot;no results&quot;** if there are no results (either a label or one table view cell?).

Is there an easiest way to do this?

*I would try a `label` behind the `tableview` then hide one of the two based on the results, but since I&#39;m working with a `TableViewController` and not a normal `ViewController` I&#39;m not sure how smart or doable that is.*

I&#39;m also using `Parse` and subclassing as a `PFQueryTableViewController`:

    @interface TableViewController : PFQueryTableViewController

I can provide any additional details needed, just let me know!

**`TableViewController` Scene in Storyboard:**

![enter image description here][1]

**EDIT:** Per Midhun MP, here&#39;s the code I&#39;m using

    - (NSInteger)numberOfSectionsInTableView:(UITableView *)tableView
    {
        NSInteger numOfSections = 0;
        if ([self.stringArray count] &gt; 0)
        {
            self.tableView.separatorStyle = UITableViewCellSeparatorStyleSingleLine;
            numOfSections                 = 1;
            //yourTableView.backgroundView   = nil;
            self.tableView.backgroundView = nil;
        }
        else
        {
            UILabel *noDataLabel         = [[UILabel alloc] initWithFrame:CGRectMake(0, 0, self.tableView.bounds.size.width, self.tableView.bounds.size.height)];
            noDataLabel.text             = @&quot;No data available&quot;;
            noDataLabel.textColor        = [UIColor blackColor];
            noDataLabel.textAlignment    = NSTextAlignmentCenter;
            //yourTableView.backgroundView = noDataLabel;
            //yourTableView.separatorStyle = UITableViewCellSeparatorStyleNone;
            self.tableView.backgroundView = noDataLabel;
            self.tableView.separatorStyle = UITableViewCellSeparatorStyleNone;
        }
        
        return numOfSections;
    }

And here&#39;s the View I&#39;m getting, it still has separator lines.  I get the feeling that this is some small change, but I&#39;m not sure why separator lines are showing up?

![enter image description here][2]


  [1]: http://i.stack.imgur.com/MN2Oz.png
  [2]: http://i.stack.imgur.com/St3pF.png

If no Table View results, display &quot;No Results&quot; on screen

I was trying to upload an image file to Parse after taking photo directly on phone. But it throws an exception: 

&gt;Terminating app due to uncaught exception &#39;NSInvalidArgumentException&#39;, reason: &#39;PFFile cannot be larger than 10485760 bytes&#39;

Here is my code: 

In first view controller:

    override func prepareForSegue(segue: UIStoryboardSegue, sender: AnyObject?) {
        if (segue.identifier == &quot;getImage&quot;)
        {
            var svc = segue.destinationViewController as! ClothesDetail
            svc.imagePassed = imageView.image
        }
    }

In view controller that uploads image:

    let imageData = UIImagePNGRepresentation(imagePassed)
    let imageFile = PFFile(name: &quot;\(picName).png&quot;, data: imageData)

    var userpic = PFObject(className:&quot;UserPic&quot;)
    userpic[&quot;picImage&quot;] = imageFile`


But I still need to upload that photo to Parse. Is there any way to reduce the size or resolution of the image?

How to compress of reduce the size of an image before uploading to Parse as PFFile? (Swift)

This was simply an update that didn&#39;t change anything to do with the rejection reason. Here is the response from the resolution center:


&gt; Reasons
&gt; Program License Agreement
&gt; PLA 3.3.12

&gt; We found your app uses the iOS Advertising Identifier but does not include ad functionality. This does not comply with the terms of the iOS Developer Program License Agreement, as required by the App Store Review Guidelines.

&gt; Specifically, section 3.3.12 of the iOS Developer Program License Agreement states:

&gt; &quot;You and Your Applications (and any third party with whom you have contracted to serve advertising) may use the Advertising Identifier, and any information obtained through the use of the Advertising Identifier, only for the purpose of serving advertising. If a user resets the Advertising Identifier, then You agree not to combine, correlate, link or otherwise associate, either directly or indirectly, the prior Advertising Identifier and any derived information with the reset Advertising Identifier.&quot;

&gt; Please check your code - including any third-party libraries - to remove any instances of:

&gt; class: **ASIdentifierManager**&lt;br&gt;
selector: **advertisingIdentifier**&lt;br&gt;
framework: **AdSupport.framework**

&gt; If you are planning to incorporate ads in a future version, please remove the Advertising Identifier from your app until you have included ad functionality.

&gt; To help locate the Advertising Identifier, use the “nm” tool. For information on the “nm” tool, open a terminal window and enter, “man nm.” 

&gt; If you do not have access to the libraries source, you may be able to search the compiled binary using the &quot;strings&quot; or &quot;otool&quot; command line tools. The &quot;strings&quot; tool lists the methods that the library calls, and &quot;otool -ov&quot; will list the Objective-C class structures and their defined methods. These techniques can help you narrow down where the problematic code resides.


The third party libraries I&#39;m using is the latest version of `parse.com sdk, latest version of flurry analytics, and version 2.2 of test flight`. Does anybody know which library is the issue? Thanks

My app was just rejected for using the Ad support framework. Which library is responsible?

I&#39;ve been working with the Parse SDK and I followed the quickstep guide. When I try to run, I get these 8 errors. Any ideas as to why? It looks like something to do with the Facebook part of Parse which I&#39;m not using.

     Undefined symbols for architecture armv7:
    &quot;_FBTokenInformationTokenKey&quot;, referenced from:
      -[PFFacebookTokenCachingStrategy accessToken] in Parse(PFFacebookTokenCachingStrategy.o)
      -[PFFacebookTokenCachingStrategy setAccessToken:] in Parse(PFFacebookTokenCachingStrategy.o)
     &quot;_FBTokenInformationExpirationDateKey&quot;, referenced from:
      -[PFFacebookTokenCachingStrategy cacheTokenInformation:] in     Parse(PFFacebookTokenCachingStrategy.o)
      -[PFFacebookTokenCachingStrategy expirationDate] in Parse(PFFacebookTokenCachingStrategy.o)
      -[PFFacebookTokenCachingStrategy setExpirationDate:] in Parse(PFFacebookTokenCachingStrategy.o)
     &quot;_OBJC_METACLASS_$_FBSessionTokenCachingStrategy&quot;, referenced from:
      _OBJC_METACLASS_$_PFFacebookTokenCachingStrategy in Parse(PFFacebookTokenCachingStrategy.o)
    &quot;_OBJC_CLASS_$_FBSessionTokenCachingStrategy&quot;, referenced from:
      _OBJC_CLASS_$_PFFacebookTokenCachingStrategy in Parse(PFFacebookTokenCachingStrategy.o)
    &quot;_FBTokenInformationUserFBIDKey&quot;, referenced from:
      -[PFFacebookTokenCachingStrategy facebookId] in Parse(PFFacebookTokenCachingStrategy.o)
      -[PFFacebookTokenCachingStrategy setFacebookId:] in Parse(PFFacebookTokenCachingStrategy.o)
    &quot;_OBJC_CLASS_$_FBRequest&quot;, referenced from:
      objc-class-ref in Parse(PFFacebookAuthenticationProvider.o)
    &quot;_OBJC_CLASS_$_FBSession&quot;, referenced from:
      objc-class-ref in Parse(PFFacebookAuthenticationProvider.o)
     ld: symbol(s) not found for architecture armv7
     clang: error: linker command failed with exit code 1 (use -v to see invocation)


Parse for iOS: Errors when trying to run the app

I am using Parse &amp; ParseUI.
I want my PFLoginViewController subclass to have a transparent background. In the future, I want to lay a blurred view over the background.

But.... Once the animate-in of the PFLoginViewController is done, the background turns black... Whilst during the animation the background was transparent.

	func presentLogin() {
		var loginViewController = LoginViewController()
		var signupViewController = SignUpViewController()

		loginViewController.fields = .UsernameAndPassword | .LogInButton | .PasswordForgotten | .SignUpButton | PFLogInFields.DismissButton
		signupViewController.fields = .UsernameAndPassword | .Email	| .DismissButton | .SignUpButton
		loginViewController.delegate = self
		loginViewController.logInView.backgroundColor = UIColor.clearColor()
		loginViewController.logInView.opaque = false
		signupViewController.delegate = self

		loginViewController.signUpController = signupViewController

		self.presentViewController(loginViewController, animated: true) { () -&gt; Void in
			//
		}
	}

My logincontroller&#39;s used subclass:

    class LoginViewController: PFLogInViewController {

	    @IBOutlet weak var _nmcLogoLabel: UILabel!

        override func viewDidLoad() {
            super.viewDidLoad()
    
	    	// Do any additional setup after loading the view.
	    	let userName = SettingsManager.userName
	    	let password = SettingsManager.password

    		self.logInView.usernameField.text = userName
    		self.logInView.passwordField.text = password

    		NSBundle.mainBundle().loadNibNamed(&quot;LoginViewBranding&quot;, owner: self, options: nil)[0] as? UIView
		
    		self.logInView.logo = _nmcLogoLabel

        }

    }

How can I make it transparent?

P.s. Applying the clearColor to the backgroundColor in the subclass makes no difference

Transparent background for modally presented viewcontroller

I&#39;m making an android app in Android Studio, integrating ParseCloud and when I try to retrieve some **JSONObject** from the cloud, I get this error message after step-debugging:

&gt; 12-13 13:32:34.857 25631-25638/com.parse.starter A/art: art/runtime/barrier.cc:90] Check failed: count_ == 0 (count_=-1, 0=0) Attempted to destroy barrier with non zero count

&gt; 12-13 13:32:34.858 25631-25638/com.parse.starter A/art: art/runtime/runtime.cc:366] Runtime aborting --- recursively, so no thread-specific detail!

&gt; 12-13 13:32:34.863 25631-25638/com.parse.starter A/art: art/runtime/runtime.cc:366] 

&gt; 12-13 13:32:34.882 25631-25638/com.parse.starter A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 25638 (JDWP)

Problem arises in this piece of code in **ParseDecoder.java**, precisely on the `while` line:

    Map&lt;String, Object&gt; convertJSONObjectToMap(JSONObject object) {
        Map&lt;String, Object&gt; outputMap = new HashMap&lt;&gt;();
        Iterator&lt;String&gt; it = object.keys();
        while (it.hasNext()) {
          String key = it.next();
          Object value = object.opt(key);
          outputMap.put(key, decode(value));
        }
        return outputMap;
    }

As I&#39;ve seen while debugging, the object I wait for is created and is filled with one entry, but then this happens and I&#39;m little bit lost... Any guidance will be great, thank you very much!


Logcat error message - Attempted to destroy barrier with non zero count

I am getting an error after adding this code from parse.com:

    - (void)application:(UIApplication *)application
    didReceiveRemoteNotification:(NSDictionary *)userInfo
    fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler {
        if (application.applicationState == UIApplicationStateInactive) {
            [PFAnalytics trackAppOpenedWithRemoteNotificationPayload:userInfo];
        }
    }

I don&#39;t really understand what is going on, but I am getting this warning in the log:

&gt; You&#39;ve implemented -[&lt;UIApplicationDelegate&gt;
&gt; application:didReceiveRemoteNotification:fetchCompletionHandler:], but
&gt; you still need to add &quot;remote-notification&quot; to the list of your
&gt; supported UIBackgroundModes in your Info.plist.

I think adding in your plist file `UIBackgroundModes - remote-notification` would fix the problem,

But when I do that, it changes the words to the follow:

`Required Background Modes` -&gt; `App downloads content in response to push notifications` 

Which my app doesn&#39;t do, so I am confused as to why I am doing this in the first place.


Parse warning from didReceiveRemoteNotification:fetchCompletionHandler

I need to format a date as `yyyy-MM-dd&#39;T&#39;HH:mm:ss.SSS&#39;Z&#39;` as specified by [Parse&#39;s REST API for Facebook][1]. I was wondering what the most **lightweight** solution to this would be.


  [1]: https://parse.com/docs/rest#users-login

Format Date as &quot;yyyy-MM-dd&#39;T&#39;HH:mm:ss.SSS&#39;Z&#39;&quot;

I would like to create a user from his/her Facebook credentials without using undocumented calls. I do not believe it is possible based on the current implementation of Parse Javascript Library for two known reasons:

**1.** The current implementation of the library does not support the Appcelerator HTTP client so it fails immediately. I have addressed this issue by extending the existing Parse Javascript library&#39;s ajax method to utilize the `Appcelerator HTTP client`. 

[http://www.clearlyinnovative.com/blog/post/34758524107/parse-appcelerator-titanium-the-easy-way](http://www.clearlyinnovative.com/blog/post/34758524107/parse-appcelerator-titanium-the-easy-way)

There has been approximately 2K views on the slide deck I created and about the same on the blog post, so it is pretty clear to me people want this to work.

**2.** The current implementation of the library assumes you are integrating with the Facebook Javascript library and that library does not work with Appcelerator either. In fact Appcelerator has integrated Facebook directly into the framework so there is no need for the javascript library. All of the information required to link a user account to Facebook can be easily gotten using the API calls that Appcelerator developers are already familiar with.

The original question was removed from the Parse Support forum so I am looking for a solution from a wider community.

&gt; Hi Aaron,
&gt; 
&gt; It&#39;s not helpful to other developers to promote using undocumented
&gt; APIs in the Parse library as a workaround, so I make the decision to
&gt; unlist it. I understand it might help in your particular case with
&gt; Titanium, and you&#39;re well aware of the implications of using private
&gt; APIs, but other users might overlook that warning. I hope you
&gt; understand.
&gt; 
&gt; H&#233;ctor Ramos Solutions Architect, Parse https://parse.com/help

This is the code that was too dangerous to be left visible on the forum:

    // setting auth data retrieved from Ti.Facebook login
    authData = {
        &quot;facebook&quot; : {
            &quot;id&quot; : Ti.Facebook.uid,
             &quot;access_token&quot; : Ti.Facebook.accessToken,
             &quot;expiration_date&quot; : expDate, // &quot;format: yyyy-MM-dd&#39;T&#39;HH:mm:ss.SSS&#39;Z&#39;&quot;
        }
    };
     
    // Either way I resolved the problem, calling _handleSaveResult(true) on the returned user object, 
    // I just dont think it should have been as difficult as it was
    // attempt to log the user in using the FB information
    var user = new Parse.User();
    user.save({
        &quot;authData&quot; : authData
    }).then(function(_user) {
        // force the user to become current
        _user._handleSaveResult(true); //&lt;-- this is the evil method I called
        if (!_user.existed()) {
     
            // add additional user information
            var userInfo = {
                &quot;acct_email&quot; : &quot;bryce@xxxxxx.com&quot;,
                &quot;acct_fname&quot; : &quot;Bryce&quot;,
                &quot;acct_lname&quot; : &quot;Saunders&quot;
            };
            return _user.save(userInfo);
        }
    }).then(function(_user) {
     
        alert(&#39;Hooray! Let them use the app now.&#39;);
     
    }, function(error) {
        alert(&#39; ERROR: &#39; + JSON.stringify(error, null, 2));
    });

Question on Appcelerator Forum

[http://developer.appcelerator.com/question/152146/facebook-appcelerator-and-parse-integration-need-help](http://developer.appcelerator.com/question/152146/facebook-appcelerator-and-parse-integration-need-help)

Question on Parse Forum

[https://parse.com/questions/how-do-you-integrate-the-parse-javascript-api-with-appcelerator-and-not-use-undocumented-calls](https://parse.com/questions/how-do-you-integrate-the-parse-javascript-api-with-appcelerator-and-not-use-undocumented-calls)

How do you integrate the Parse Javascript API with Appcelerator and not use undocumented calls?

When I click on login with Facebook button, it is opening safari browser and getting closed immediately. Noticed error on the console.

App delegate method:

    func application(app: UIApplication, openURL url: NSURL, options: [String : AnyObject]) -&gt; Bool {
        print(&quot;###### URL : &quot;)
        print(url)
        print(&quot;###### App : &quot;)
        print(app)
        print(options[&quot;UIApplicationOpenURLOptionsSourceApplicationKey&quot;])
        return FBSDKApplicationDelegate.sharedInstance().application(app, openURL: url,  sourceApplication: options[&quot;UIApplicationOpenURLOptionsSourceApplicationKey&quot;] as! String,
                annotation: nil)
    }

&lt;pre&gt;
2015-09-18 18:37:51.410 [21036:5050465] -canOpenURL: failed for URL: &quot;fbauth2:///&quot; - error: &quot;(null)&quot;

2015-09-18 18:37:51.417[21036:5050465] -canOpenURL: failed for URL: &quot;fbauth2:///&quot; - error: &quot;(null)&quot;

###### URL : 

fb4554284912963222://authorize/?error_code=100&amp;error_message=Invalid+Scope%3A+public&amp;state=%7B%22challenge%22%3A%222ZmK6R5F05d%252F060TkCqj8SjPLjc%253D%22%2C%220_auth_logger_id%22%3A%223C79F2C8-61B9-470E-AE1B-E1C68435DB83%22%2C%22com.facebook.sdk_client_state%22%3Atrue%2C%223_method%22%3A%22sfvc_auth%22%7D&amp;e2e=%7B%22init%22%3A145973.000512302%7D#_=_

###### App : 

&lt;UIApplication: 0x7f9cf2d17770&gt;
Optional(com.apple.SafariViewService)
nil

###### err:

Optional(Error Domain=com.facebook.sdk.core Code=8 &quot;(null)&quot; UserInfo={com.facebook.sdk:FBSDKGraphRequestErrorGraphErrorCode=100, com.facebook.sdk:FBSDKErrorDeveloperMessageKey=Invalid Scope: public, com.facebook.sdk:FBSDKGraphRequestErrorCategoryKey=0})
&lt;/pre&gt;

IDE : xcode 7  
Language : Swift2  
Facebook SDK : 4.6.0  
Parse: 1.8.4

I have also verified .plist is having all keys which are required.
Also verified the bundle identifier for typo mistakes. All look good.
Facebook is active.

 
Any help?


facebook login issue - canOpenURL: failed for URL: &quot;fbauth2:///&quot; - error: &quot;(null)&quot;

I&#39;m developing with parse.com and I get this problem upgrading to Xcode 7. Some Parse Frameworks are not fully working.

I&#39;ve got this Warning:

&gt; URGENT: all bitcode will be dropped because
&gt; &#39;/Users/[MY_USER]/Downloads/parse-starter-project-1/ParseStarterProject/Parse.framework/Parse(PFMutableFileState.o)&#39;
&gt; was built without bitcode. You must rebuild it with bitcode enabled
&gt; (Xcode setting ENABLE_BITCODE), obtain an updated library from the
&gt; vendor, or disable bitcode for this target. Note: This will be an
&gt; error in the future.

Let me remind that everything was working in the last version of Xcode 6.

**How to ENABLE Bitcode in Xcode 7?** 


How to ENABLE_BITCODE in Xcode 7?

I keep getting 

&gt; &quot;Error Domain=com.facebook.sdk.login Code=308 &quot;The operation couldn’t
&gt; be completed. (com.facebook.sdk.login error 308.)&quot;&quot;

 upon trying to login with Facebook from my device.

My code works on the simulator, but not on an actual device. Has anyone ran into this error code before? I&#39;ll be more than happy to share code upon request.

FBSDK Login Error Code: 308 in Objective-C

I&#39;ve been considering using Parse.com&#39;s service for my backend, but I&#39;m skeptical about its scalability.

Can it *really* handle several thousand simultaneous users?  If not, is their any good way transitioning away from it?  

How scalable is Parse?

I have encountered this keyword in various occasions. I kind of know what it&#39;s suppose to do. But I really want a better understanding of it. 

What I noticed about `@NSManaged` - based not on documentation, but through repeated use:

1. It magically replaces key value coding. 
2. It is roughly equivalent to `@dynamic` in Objective-C (which I don&#39;t know much about)
3. I need it to subclass `PFObject` from the `Parse SDK`. It normally uses KVC to read/write values from/to the backend.
4. Prefixing any variable with `@NSManaged` will shut the compiler up when I don&#39;t initialize within the initializer. 

**The formal definition (in the Core Data Apple Docs):**

&gt;Core Data provides the underlying storage and implementation of properties in subclasses of the NSManagedObject class. Add the @NSManaged attribute before each property definition in your managed object subclass that corresponds to an attribute or relationship in your Core Data model. Like the @dynamic attribute in Objective-C, the @NSManaged attribute informs the Swift compiler that the storage and implementation of a property will be provided at runtime. However, unlike @dynamic, the @NSManaged attribute is available only for Core Data support.

**What I got from that:**

&gt;Variables with `@NSManaged` shall be exempt from compile time checks for *something*.


I&#39;ve read the formal documentation and various other SO questions regarding this matter:

https://stackoverflow.com/questions/1160498/synthesize-vs-dynamic-what-are-the-differences

https://stackoverflow.com/questions/4524954/what-is-common-case-for-dynamic-usage/4524983#4524983


I instinctively recognize *some* scenarios where I should use it. I *partially* know what it does. But what I seek is purer understanding of what it does. 

**Further Observations:**

A `PFObject` in the `Parse SDK` relies on `Key Value Coding` to access its values. The `PFObject` provides the following accessors:

`objectForKey:`  

    let score = results.objectForKey(&quot;descriptionOfResult&quot;) 
    //returns the descriptionOfResult value from the results object

`setObject:forKey:`

    results.setObject(&quot;The results for a physics exam&quot;, forKey: &quot;descriptionOfResult&quot;) 
    //sets the value of descriptionOfResult 

To my understanding, `@NSManaged` *magically* understands that the variable I&#39;ve declared automatically uses the above accessors to `get` and `set`. I&#39;d like to know how it does that (if what I understand is true), and whatever else it does.

What does @NSManaged do?

I am trying to use an Objective-C framework with the Swift programming language for iOS 8 development. This is a specific case of an import but the general problem is: 

**How do you import an Objective-C framework into swift and get the import recognized?**

I am trying to integrate the Parse framework into a swift application using the iOS 8 and Xcode 6 betas. 

Here is the technique for Parse framework integration in Objective-C: 

https://www.parse.com/apps/quickstart#social/mobile/ios/native/existing

I have downloaded the Parse framework as a compressed archive, extracted it, and imported it into Xcode 6 without any problems. Within my application it appears as a properly formatted framework under the name Parse.framework. 

My current thought process is to modify the `AppDelegate.swift` file in the root directory of my project. Here is the current file without modifications (automatically generated by Xcode upon swift project creation): 

https://gist.github.com/fconcklin/e8ef7d8b056105a04161

I have tried to import parse by adding the line `import Parse` below the line `import UIKit`. However, Xcode issues a warning that there is no such module found and the build fails.

I also tried creating a file `${PROJ_NAME_HERE}-Bridging-Header.h` that contains the Objective-C import of Parse using `import &lt;Parse/Parse.h&gt;`. This line doesn&#39;t throw an error but appears to ultimately make no difference. 


All Parse Platform Solutions on Gang of Coders

Total of 17 Parse Platform Solutions

Impact of Xcode build options "Enable bitcode" Yes/No