Had this warning when I forgot to enable code coverage:

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/oJLGm.png

**Xcode 10+** 

Enable Code Coverage for Test scheme.

[![enter image description here][1]][1]


  [1]: https://i.stack.imgur.com/vHFre.png

Cleaning my build folder eliminated the error for me. (Option-Shift-Command K.) I&#39;m using Xcode Version 9.2 (9C40b). The error started when I added a set of images to my Assets.xcassets. After a full clean the error is gone.

&lt;s&gt;Try setting `CLANG_ENABLE_CODE_COVERAGE = NO` in your build settings for the target being tested and the tests themselves.&lt;/s&gt;

**Edit**: Please see the answer by @kasyanov-ms.

This may not be helpful to anyone else, but I was hitting this when I had placed a `exit(EXIT_FAILURE)` in my code while refactoring a piece of code. I had assumed putting it in would crash the app right there and show me that it crashed there, but instead it was giving me this error and not showing where it had crashed.

**Xcode 11 beta 1:**

This is a known issue when attempting to use code coverage against simulator targets. You must either use a later beta or run coverage against a physical device. 

I want select from Firestore collection just articles written NOT by me.
&lt;br&gt;Is it really so hard?

&gt; Every article has field &quot;owner_uid&quot;.

Thats it: &lt;br&gt;I JUST want to write equivalent to `&quot;select * from articles where uid&lt;&gt;request.auth.uid&quot;`


**TL;DR: solution found already:** usages for languages/platforms: https://firebase.google.com/docs/firestore/query-data/queries#kotlin+ktx_5

Firestore: how to perform a query with inequality / not equals

After updating my dependency versions in **`AndroidStudio3.1`**, I started getting the following error:

        Information:Gradle tasks [:app:assembleDebug]
    Error:com.android.builder.dexing.DexArchiveBuilderException: Failed to process C:\Users\Blabla\.gradle\caches\modules-2\files-2.1\com.google.guava\guava\21.0\3a3d111be1be1b745edfa7d91678a12d7ed38709\guava-21.0.jar
    Error:com.android.builder.dexing.DexArchiveBuilderException: Error while dexing.
    Error:com.android.tools.r8.ApiLevelException: Default interface methods are only supported starting with Android N (--min-api 24): java.util.Collection com.google.common.collect.BiMap.values()
    Error:Execution failed for task &#39;:app:transformClassesWithDexBuilderForDebug&#39;.
    &gt; com.android.build.api.transform.TransformException: com.android.builder.dexing.DexArchiveBuilderException: com.android.builder.dexing.DexArchiveBuilderException: Failed to process C:\Users\Blabla\.gradle\caches\modules-2\files-2.1\com.google.guava\guava\21.0\3a3d111be1be1b745edfa7d91678a12d7ed38709\guava-21.0.jar
    Information:BUILD FAILED in 6s
    Information:4 errors
    Information:0 warnings
    Information:See complete output in console

I have already cleaned and rebuilt project. Checked my **`&quot;multiDexEnabled true&quot;`** and &#39;compile **`&#39;com.android.support:multidex:1.0.2&#39;`** is added.

 What else can I do?

EDIT: Adding build.gradle

    apply plugin: &#39;com.android.application&#39;
    
    android {
        compileSdkVersion 27
        buildToolsVersion &#39;26.0.2&#39;
        defaultConfig {
            applicationId &quot;com.blabla&quot;
            minSdkVersion 19
            targetSdkVersion 27
            versionCode 1
            versionName &quot;1.0&quot;
            testInstrumentationRunner &quot;android.support.test.runner.AndroidJUnitRunner&quot;
            vectorDrawables.useSupportLibrary = true
            multiDexEnabled true
        }
        buildTypes {
            release {
                minifyEnabled false
                proguardFiles getDefaultProguardFile(&#39;proguard-android.txt&#39;), &#39;proguard-rules.pro&#39;
            }
        }
        configurations.all {
            resolutionStrategy.force &#39;com.google.code.findbugs:jsr305:1.3.9&#39;
        }

    }
    
    dependencies {
        compile fileTree(dir: &#39;libs&#39;, include: [&#39;*.jar&#39;])
        androidTestCompile(&#39;com.android.support.test.espresso:espresso-core:2.2.2&#39;, {
            exclude group: &#39;com.android.support&#39;, module: &#39;support-annotations&#39;
        })
        compile &#39;com.android.support:appcompat-v7:27.0.0&#39;
        compile &#39;com.android.support.constraint:constraint-layout:1.0.2&#39;
        compile &#39;com.android.support:multidex:1.0.2&#39;
        compile &#39;com.android.support:design:27.0.0&#39;
        compile &#39;com.android.support:cardview-v7:27.0.0&#39;
        compile &#39;com.jakewharton:butterknife:8.7.0&#39;
        compile &#39;com.google.code.gson:gson:2.8.0&#39;
        compile &#39;com.google.guava:guava:21.0&#39;
        compile &#39;com.microsoft.azure:azure-mobile-android:3.2.0@aar&#39;
        compile &#39;com.microsoft.azure:notification-hubs-android-sdk:0.4@aar&#39;
        compile &#39;com.microsoft.azure:azure-notifications-handler:1.0.1@aar&#39;
        compile &#39;com.squareup.okhttp:okhttp:2.5.0&#39;
        compile &#39;com.google.firebase:firebase-core:11.4.2&#39;
        compile &#39;com.google.firebase:firebase-crash:11.4.2&#39;
        compile &#39;com.google.firebase:firebase-auth:11.4.2&#39;
        compile &#39;com.google.firebase:firebase-database:11.4.2&#39;
        compile &#39;com.google.firebase:firebase-storage:11.4.2&#39;
        testCompile &#39;junit:junit:4.12&#39;
        annotationProcessor &#39;com.jakewharton:butterknife-compiler:8.7.0&#39;
        compile &#39;com.google.android.gms:play-services-maps:11.4.2&#39;
        compile &#39;com.google.android.gms:play-services-location:11.4.2&#39;
        compile &#39;com.google.maps.android:android-maps-utils:0.5+&#39;
    }
    apply plugin: &#39;com.google.gms.google-services&#39;



Error:com.android.builder.dexing.DexArchiveBuilderException: Failed to process guava-21.0.jar Android 3.1 Dev Channel

I&#39;m getting the error `LLVM Profile Error: Failed to write file &quot;default.profraw&quot;: Permission denied` after running unit tests in Xcode. I don&#39;t know where Xcode is trying to write this file to. 

What folder should I grant permissions for?

LLVM Profile Error: Failed to write file &quot;default.profraw&quot;: Permission denied

<p>I'm getting the error <code>LLVM Profile Error: Failed to write file "default.profraw": Permission denied</code> after running unit tests in Xcode. I don't know where Xcode is trying to write this file to.</p>
<p>What folder should I grant permissions for?</p>


Using Xcode 9.1, after building an iOS app, I want to archive it and upload it to the appStore for beta-testing.
But I get the following issue after clicking the button `Upload to the App Store...` and choosing `Automatically manage signing`:

&gt; &quot;My Name&quot; has one iOS Distribution certificate but its private key is
&gt; not installed. Contact the creator of this certificate to get a copy of the private key.

I do not know why this &quot;private key is not installed&quot;, but the Distribution certificate may have been created on a different computer or something. In any case:

What is the simplest way to retrieve the missing private key and install it? In order to make things work.


Distribution certificate / private key not installed

The device&#39;s data is no longer present at _/Users/[user name]/Library/Developer/CoreSimulator/Devices/D651BCC7-29FD-4B91-82F6-E255E856EA2F/data._

I uninstalled xcode 9 and installed xcode 9.1, but when run project, following message was shown:

&gt; Unable to boot device because it cannot be located on disk.
The device&#39;s data is no longer present at /Users/[user name]/Library/Developer/CoreSimulator/Devices/D651BCC7-29FD-4B91-82F6-E255E856EA2F/data.

I found &quot;Developer&quot; folder, but cannot find &quot;CoreSimulator&quot; folder.


Unable to boot device because it cannot be located on disk

Warning: `leading or trailing horizontal alignment before iOS 11`

I am getting above warning during compilation on Xcode 9.1 on one of the scenes in a storyboard file. There are other storyboards *(with deployment target iOS 10.0)* and yet the warning is shown to this specific scene on a specific Storyboard file.

The warning gets suppressed if I change deployment target to iOS 11.0 on the scene where warning is shown but I don&#39;t want to do that.

Has anyone come across this case?

leading or trailing horizontal alignment before iOS 11

Working with my first application for learning purposes. It goes well but has met into a problem with Xcode. When I try to run the application on the iPhone simulator this message always pops up &quot;This app could not be installed at this time.&quot; 

[![screenshot][1]][1]

What is wrong? There are no errors when trying to build the app. Has tried to clean the build. Reinstall pods. Restarted Xcode. Erased all settings on the simulator device, however, the problems still exist. 

The error message does not give me any information. Is there another logfile I could look into or something? 


  [1]: https://i.stack.imgur.com/5Ahpd.png

Xcode: &quot;This app could not be installed at this time.&quot;

I have a simple program HelloWorld running on iOS. The same code has been running fine for a long time. Recently, I notice that I get the below BoringSSL error when the program runs on my ipad connected to Xcode 9 on my Macbook. I don&#39;t see this error when I run the program in simulator. The iOS is 11.2. Xcode is 9.2.

My code has no reference to BoringSSL. However, it does use NSMutableURLRequest to make https call to a server. The call works fine and everything seems to work fine except the BoringSSL messages.

Is there a way the I can debug why the message comes up? HellowWorld[466:85961], what do those 2 numbers mean? 

What does the message mean and how to avoid it?

    2017-12-13 15:41:13.486047-0500 HellowWorld[466:85961] [BoringSSL] Function boringssl_session_errorlog: line 2871 [boringssl_session_read] SSL_ERROR_ZERO_RETURN(6): operation failed because the connection was cleanly shut down with a close_notify alert
    2017-12-13 15:41:13.486363-0500 HellowWorld[466:85961] [BoringSSL] Function boringssl_session_errorlog: line 2871 [boringssl_session_read] SSL_ERROR_ZERO_RETURN(6): operation failed because the connection was cleanly shut down with a close_notify alert

[![Screenshot added][1]][1]


  [1]: https://i.stack.imgur.com/cCLOV.png

Xcode 9 iOS 11 BoringSSL SSL_ERROR_ZERO_RETURN

I know that an *&quot;undefined behaviour&quot;* in C++ can pretty much allow the compiler to do anything it wants. However, I had a crash that surprised me, as I assumed that the code was safe enough.

In this case, the real problem happened only on a specific platform using a specific compiler, and only if optimization was enabled.

I tried several things in order to reproduce the problem and simplify it to the maximum. Here&#39;s an extract of a function called `Serialize`, that would take a bool parameter, and copy the string `true` or `false` to an existing destination buffer.

Would this function be in a code review, there would be no way to tell that it, in fact, could crash if the bool parameter was an uninitialized value?

    // Zero-filled global buffer of 16 characters
    char destBuffer[16];
    
    void Serialize(bool boolValue) {
        // Determine which string to print based on boolValue
        const char* whichString = boolValue ? &quot;true&quot; : &quot;false&quot;;
        
        // Compute the length of the string we selected
        const size_t len = strlen(whichString);
        
        // Copy string into destination buffer, which is zero-filled (thus already null-terminated)
        memcpy(destBuffer, whichString, len);
    }

If this code is executed with clang 5.0.0 + optimizations, it will/can crash.

The expected ternary-operator `boolValue ? &quot;true&quot; : &quot;false&quot;` looked safe enough for me, I was assuming, &quot;Whatever garbage value is in `boolValue` doesn&#39;t matter, since it will evaluate to true or false anyhow.&quot;

I have setup a [Compiler Explorer example](https://godbolt.org/z/DoFmhA) that shows the problem in the disassembly, here the complete example. *Note: in order to repro the issue, the combination I&#39;ve found that worked is by using Clang 5.0.0 with -O2 optimisation.*

    #include &lt;iostream&gt;
    #include &lt;cstring&gt;
    
    // Simple struct, with an empty constructor that doesn&#39;t initialize anything
    struct FStruct {
        bool uninitializedBool;
        
       __attribute__ ((noinline))  // Note: the constructor must be declared noinline to trigger the problem
       FStruct() {};
    };
    
    char destBuffer[16];
    
    // Small utility function that allocates and returns a string &quot;true&quot; or &quot;false&quot; depending on the value of the parameter
    void Serialize(bool boolValue) {
        // Determine which string to print depending if &#39;boolValue&#39; is evaluated as true or false
        const char* whichString = boolValue ? &quot;true&quot; : &quot;false&quot;;
        
        // Compute the length of the string we selected
        size_t len = strlen(whichString);
        
        memcpy(destBuffer, whichString, len);
    }
    
    int main()
    {
        // Locally construct an instance of our struct here on the stack. The bool member uninitializedBool is uninitialized.
        FStruct structInstance;
        
        // Output &quot;true&quot; or &quot;false&quot; to stdout
        Serialize(structInstance.uninitializedBool);
        return 0;
    }

The problem arises because of the optimizer: It was clever enough to deduce that the strings &quot;true&quot; and &quot;false&quot; only differs in length by 1. So instead of really calculating the length, it uses the value of the bool itself, which *should* technically be either 0 or 1, and goes like this:

    const size_t len = strlen(whichString); // original code
    const size_t len = 5 - boolValue;       // clang clever optimization

While this is &quot;clever&quot;, so to speak, my question is: **Does the C++ standard allow a compiler to assume a bool can only have an internal numerical representation of &#39;0&#39; or &#39;1&#39; and use it in such a way?**

Or is this a case of implementation-defined, in which case the implementation assumed that all its bools will only ever contain 0 or 1, and any other value is undefined behaviour territory?

Content Type	Original Author	Original Content on Stackoverflow
Question	Cloud9999Strife	View Question on Stackoverflow
Solution 1 - Xcode	kasyanov-ms	View Answer on Stackoverflow
Solution 2 - Xcode	muhasturk	View Answer on Stackoverflow
Solution 3 - Xcode	John Pavley	View Answer on Stackoverflow
Solution 4 - Xcode	Coder-256	View Answer on Stackoverflow
Solution 5 - Xcode	EndersJeesh	View Answer on Stackoverflow
Solution 6 - Xcode	Allison	View Answer on Stackoverflow

LLVM Profile Error: Failed to write file "default.profraw": Permission denied

Xcode Problem Overview

Xcode Solutions

Solution 1 - Xcode

Solution 2 - Xcode

Solution 3 - Xcode

Solution 4 - Xcode

Solution 5 - Xcode

Solution 6 - Xcode

Error:com.android.builder.dexing.DexArchiveBuilderException: Failed to process guava-21.0.jar Android 3.1 Dev Channel

Firestore: how to perform a query with inequality / not equals

Attributions