iOS Question SOLVED: Can't compile with 10.0 - Copilot says it is because "The Hosted Builder is still running an older B4i version than your IDE."

[JackKirk]

Having all sorts of problems trying to compile my major B4i app.

I was on 8.9 - but the compiler gave messages that the forum suggested I needed to upgrade to 10.0

Upgraded to 10.0 and now the compiler is giving a great slew of messages ending with:

Error: ** BUILD FAILED **


The following build commands failed:
ScanDependencies /Users/administrator/Documents/UploadedProjects/<user id>/build/B4iProject.build/Release-iphoneos/B4iProject.build/Objects-normal/arm64/b4i_xml_2_map.o /Users/administrator/Documents/UploadedProjects/<user id>/B4iProject/b4i_xml_2_map.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'B4iProject' from project 'B4iProject')
ScanDependencies /Users/administrator/Documents/UploadedProjects/<user id>/build/B4iProject.build/Release-iphoneos/B4iProject.build/Objects-normal/arm64/b4i_web_view.o /Users/administrator/Documents/UploadedProjects/<user id>/B4iProject/b4i_web_view.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'B4iProject' from project 'B4iProject')
ScanDependencies /Users/administrator/Documents/UploadedProjects/<user id>/build/B4iProject.build/Release-iphoneos/B4iProject.build/Objects-normal/arm64/b4i_video_player.o /Users/administrator/Documents/UploadedProjects/<user id>/B4iProject/b4i_video_player.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'B4iProject' from project 'B4iProject')
ScanDependencies /Users/administrator/Documents/UploadedProjects/<user id>/build/B4iProject.build/Release-iphoneos/B4iProject.build/Objects-normal/arm64/b4i_utilit_ies.o /Users/administrator/Documents/UploadedProjects/<user id>/B4iProject/b4i_utilit_ies.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'B4iProject' from project 'B4iProject')
ScanDependencies /Users/administrator/Documents/UploadedProjects/<user id>/build/B4iProject.build/Release-iphoneos/B4iProject.build/Objects-normal/arm64/b4i_talk_2_us.o /Users/administrator/Documents/UploadedProjects/<user id>/B4iProject/b4i_talk_2_us.m normal arm64 objective-c com.apple.compilers.llvm.clang.1_0.compiler (in target 'B4iProject' from project 'B4iProject')
(5 failures)

When I throw this at MS Copilot it comes back with:

Those five failing `.m` files tell us something extremely specific — and it’s good news, because it narrows the problem dramatically.

Let’s decode what this pattern really means and then I’ll give you the next precise isolation step.

---

# What the new failures reveal

The failing files are:

- `b4i_xml_2_map.m`
- `b4i_web_view.m`
- `b4i_video_player.m`
- `b4i_utilit_ies.m`
- `b4i_talk_2_us.m`

Three of these are **core B4i framework wrappers**:

| File | Underlying library |
|------|--------------------|
| `b4i_web_view.m` | iWebView / WKWebView |
| `b4i_video_player.m` | iMedia / VideoPlayer |
| `b4i_xml_2_map.m` | XML / Map utilities |

The other two (`b4i_utilit_ies.m`, `b4i_talk_2_us.m`) are **generated from your own modules**.

When *multiple unrelated generated files* all fail at the **ScanDependencies** stage, that almost always means:

> **The Hosted Builder is still running an older B4i version than your IDE.**

Because if the builder’s toolchain is older, *every* generated `.m` file that references new symbols or new headers will fail during dependency scanning.

This is why the set of failing files keeps growing as you test more.

---

# Why this is almost certainly a builder-version mismatch

If the problem were:

- a single bad library
- a single bad module
- a single malformed Objective‑C block

…you would see **one** `.m` file failing consistently.

But you’re seeing **five different files**, from **different subsystems**, all failing at the same stage.

That only happens when:

- Xcode on the Hosted Builder
- is using an older B4i build template
- that doesn’t match the Objective‑C generated by B4i 10.0.

This exact pattern has shown up every time the IDE is updated before the Hosted Builder is updated.

 

[Erel]

The hosted builders are of course compatible with B4i v10.

The actual error is missing in those logs. Please post the full text as an attachment.

 

[JackKirk]

Please post the full text as an attachment.

Erel, thanks for looking into this.

I should note that the app compiled a couple of days ago on 8.9 without problems.

Only change made this end is upgrading to 10.0

The complete dump is in the attachment.

Thanks again...

 

[JackKirk]

Dug into the dump a bit and noticed this at top of error messages:

Error: security: SecKeychainDelete: The specified keychain could not be found.

 

[Erel]

Error: security: SecKeychainDelete: The specified keychain could not be found.

I think that this message is added by Xcode compiler to confuse the developer. The actual error is:

error: 'iCPP.h' file not found

In 99% of the cases you need to search for "error:" (lowercase) to find the real error.

Remove iCPP library from your project. It is no longer needed.

 

[JackKirk]

I think that this message is added by Xcode compiler to confuse the developer.

It sure worked on me

Remove iCPP library from your project. It is no longer needed.

That did the trick - many thanks Erel