xcode

How to detect declared but undefined functions in C++?

坚强是说给别人听的谎言 提交于 2021-02-04 22:06:28
问题 The following compiles, links and runs just fine (on Xcode 5.1 / clang): #include <iostream> class C { int foo(); }; int main(int argc, const char * argv[]) { C c; cout << "Hello world!"; } However, C::foo() is not defined anywhere, only declared. I don't get any compiler or linker warnings / errors, apparently because C::foo() is never referenced anywhere. Is there any way I can emit a warning that in the whole program no definition for C::foo() exists even though it is declared? An error

Flutter ios build for testing

核能气质少年 提交于 2021-02-04 17:18:22
问题 I would Like to know how I can build a release app without registering it to the app store. I would Like to have the APK file and share it with friends for testing purposes without registering the app. Cant find information connected with this. Thanks! UPDATE: Found solution for getting .ipa file which was installed with Cydia Impactor on a real device: # flutter build flutter build ios --release --no-codesign # make folder, add .app then zip it and rename it to .ipa mkdir -p Payload mv .

iOS中,Framework和.a的打包及使用

最后都变了- 提交于 2021-02-04 11:40:53
最近在做一个小项目,需要给客户一个demo测试,有一部分核心代码暂时不想让客户知道,就想到了打包成framework或.a库。库有两种: 静态库:.a和.framework 动态库:.tbd和.framework 静态库和动态库的区别 .a文件肯定是静态库,. tbd肯定是动态库,.framework可能是静态库也可能是动态库 静态库在链接时,会被完整的复制到可执行文件中,如果多个App都使用了同一个静态库,那么每个App都会拷贝一份,缺点是浪费内存。类似于定义一个基本变量,使用该基本变量是是新复制了一份数据,而不是原来定义的; 动态库不会复制,只有一份,程序运行时动态加载到内存中,系统只会加载一次,多个程序共用一份,节约了内存。类似于使用变量的内存地址一样,使用的是同一个变量; 但是项目中如果使用了自己定义的动态库,苹果是不允许上架的,在iOS8.0以后苹果开放了动态加载. tbd的接口,用于挂载. tbd动态库 使用静态库的好处 模块化,分工合作 避免少量改动经常导致大量的重复编译连接 也可以重用,注意不是共享使用 使用动态库的好处 使用动态库,可以将最终可执行文件体积缩小 使用动态库,多个应用程序共享内存中得同一份库文件,节省资源 使用动态库,可以不重新编译连接可执行程序的前提下,更新动态库文件达到更新应用程序的目的。 静态库的使用场景 保护自己的核心代码

Xcode 4.6 error - Timed out waiting for app to launch

 ̄綄美尐妖づ 提交于 2021-02-04 10:45:19
问题 I am building an app in Release, and running on an iPhone 4s. When I click on run, everything works well, my application even runs on the iPhone. But after some times, I have an error from Xcode : "Timed out waiting for app to launch" while my app is still running. How to deal with it? 回答1: Check which provisioning you are using, it seems that ad-hoc provisioning cannot be used for debugging. If your problem is not solve with above instruction then also try these: Stop the app from running in

Test Rich Notifications in Simulator

感情迁移 提交于 2021-02-04 07:29:08
问题 I am able to test the normal notifications in Simulator, but when I tried to test rich notifications nothing happens, event title is not getting updated. Could you please assist me, how to proceed. Do I need to change any simulator settings? I am using Xcode 11.4 Sample Payload : { "aps": { "mutable-content": 1, "alert": { "body": "Push notification body", "title": "Push notification title" } }, "media-url": "https://i.imgur.com/t4WGJQx.jpg" } NotificationService Extension Method: - (void

Unity接入第三方iOS SDK——之微信开放平台

泄露秘密 提交于 2021-02-03 08:50:11
废言 这算是Unity接入微信开放平台的第二篇了,第一篇在这: Unity接入第三方Android SDK——之微信开放平台 。 作为一个既没有接触过Android开发、有没有接触过iOS开发的人员 ,完成Android和iOS的微信SDK接入,拢共花费了一周的工作时间,效率有点低。 在完成微信SDK接入的过程中,查看过网络上不少的文章,不过似乎没有哪一篇是能文章能够一气呵成解决问题的,因此自己有了斗胆一试的想法,所以才有了这两篇文章的诞生,希望能够后面接触的小伙伴节约一些时间。 本文的亮点 最后的完成品,不需要在Xcode中修改、添加任何内容,直接Unity编译到Xcode然后安装到真机 一、开始 Universal Links的配置 这部分的内容我就不细讲了,相对比较简单,主要是苹果开发者和微信开发者后台的设置,然后把apple-app-site-association这个文件放到域名根目录即可(域名必须支持HTTPS) apple-app-site-association 这个文件的内容类似下面这样: { "applinks": { "apps": [], "details": [{ "appID": "TeamID.com.yourapp.bundleID", "paths": ["*"] } ] } } 复制代码 二、微信SDK的导入 前往微信开放平台下载SDK:

mac下Appium环境配置

风格不统一 提交于 2021-02-03 07:00:23
一、Appium环境搭建 1、xcode(需要OS X版本支持): 下载对应版本的xcode(支持对应手机系统),解压,拖入应用程序。 xcode下载地址: https://developer.apple.com/download/more/ 2、安装appium: 安装node、brew、nmp、carthage等: http://www.jianshu.com/p/efa9ac4900a6 1)如果有旧版本的appium,需要先卸载旧版本的appium:npm uninstall -g appium 2)下载appium1.6.5正式版: https://github.com/appium/appium/releases/tag/v1.6.5 ,终端进入文件目录,命令行安装:npm install。 验证安装成功:终端输入“appium -v”,出现版本号表示安装成功。   此处有坑:appium-desktop 1.6.4及以下不支持xcode9.0.1,(请注意自己的xcode版本和appium版本,要不然会报错) 3)与系统进行关联:npm link 4)安装appium桌面程序: https://github.com/appium/appium-desktop/releases/tag/v1.2.0 ,下载zip包,解压,拖入应用程序。 5

The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile

為{幸葍}努か 提交于 2021-02-02 17:57:16
问题 I have submitted many app builds to TestFlight, even yesterday, but today when I tried to submit my app to TestFlight via XCODE I get the following error: ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '[ ]' for the key 'com.apple.developer.healthkit.access' in 'Payload/Runner.app

The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile

佐手、 提交于 2021-02-02 17:54:21
问题 I have submitted many app builds to TestFlight, even yesterday, but today when I tried to submit my app to TestFlight via XCODE I get the following error: ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '[ ]' for the key 'com.apple.developer.healthkit.access' in 'Payload/Runner.app

The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile

柔情痞子 提交于 2021-02-02 17:53:43
问题 I have submitted many app builds to TestFlight, even yesterday, but today when I tried to submit my app to TestFlight via XCODE I get the following error: ERROR ITMS-90164: "Invalid Code Signing Entitlements. The entitlements in your app bundle signature do not match the ones that are contained in the provisioning profile. According to the provisioning profile, the bundle contains a key value that is not allowed: '[ ]' for the key 'com.apple.developer.healthkit.access' in 'Payload/Runner.app