看crash堆栈并没有调用到WXApi的接口,确认是在registerApp:universalLink:发生crash?
+[WXApi registerApp:universalLink:]为什么iOS调用直接崩溃?编译没错,调用的时候崩溃 调用堆栈 *** First throw call stack: ( 0 CoreFoundation 0x00007fff23baa1ee __exceptionPreprocess + 350 1 libobjc.A.dylib 0x00007fff50864b20 objc_exception_throw + 48 2 CoreFoundation 0x00007fff23bcb054 +[NSObject(NSObject) doesNotRecognizeSelector:] + 132 3 CoreFoundation 0x00007fff23baef6c ___forwarding___ + 1436 4 CoreFoundation 0x00007fff23bb10f8 _CF_forwarding_prep_0 + 120 5 HBuilder 0x000000010c51f21b -[AppDelegate application:didFinishLaunchingWithOptions:] + 1547 6 UIKitCore 0x00007fff4756fa87 -[UIApplication _handleDelegateCallbacksWithOptions:isSuspended:restoreState:] + 232 7 UIKitCore 0x00007fff4757141f -[UIApplication _callInitializationDelegatesWithActions:forCanvas:payload:fromOriginatingProcess:] + 3980 8 UIKitCore 0x00007fff47576f6e -[UIApplication _runWithMainScene:transitionContext:completion:] + 1281 9 UIKitCore 0x00007fff46cbc3ed -[_UISceneLifecycleMultiplexer completeApplicationLaunchWithFBSScene:transitionContext:] + 122 10 UIKitCore 0x00007fff471a4aa9 _UIScenePerformActionsWithLifecycleActionMask + 83 11 UIKitCore 0x00007fff46cbceff __101-[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:]_block_invoke + 198 12 UIKitCore 0x00007fff46cbc90e -[_UISceneLifecycleMultiplexer _performBlock:withApplicationOfDeactivationReasons:fromReasons:] + 296 13 UIKitCore 0x00007fff46cbcd2c -[_UISceneLifecycleMultiplexer _evalTransitionToSettings:fromSettings:forceExit:withTransitionStore:] + 818 14 UIKitCore 0x00007fff46cbc5c1 -[_UISceneLifecycleMultiplexer uiScene:transitionedFromState:withTransitionContext:] + 345 15 UIKitCore 0x00007fff46cc0bef __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke_2 + 178 16 UIKitCore 0x00007fff470ca9d7 +[BSAnimationSettings(UIKit) tryAnimatingWithSettings:actions:completion:] + 865 17 UIKitCore 0x00007fff471c2fa7 _UISceneSettingsDiffActionPerformChangesWithTransitionContext + 240 18 UIKitCore 0x00007fff46cc090a __186-[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:]_block_invoke + 153 19 UIKitCore 0x00007fff471c2eaa _UISceneSettingsDiffActionPerformActionsWithDelayForTransitionContext + 84 20 UIKitCore 0x00007fff46cc0778 -[_UIWindowSceneFBSSceneTransitionContextDrivenLifecycleSettingsDiffAction _performActionsForUIScene:withUpdatedFBSScene:settingsDiff:fromSettings:transitionContext:lifecycleActionType:] + 381 21 UIKitCore 0x00007fff46b1ac67 __64-[UIScene scene:didUpdateWithDiff:transitionContext:completion:]_block_invoke + 657 22 UIKitCore 0x00007fff46b197ec -[UIScene _emitSceneSettingsUpdateResponseForCompletion:afterSceneUpdateWork:] + 248 23 UIKitCore 0x00007fff46b1a991 -[UIScene scene:didUpdateWithDiff:transitionContext:completion:] + 210 24 UIKitCore 0x00007fff475755cb -[UIApplication workspace:didCreateScene:withTransitionContext:completion:] + 535 25 UIKitCore 0x00007fff470ec535 -[UIApplicationSceneClientAgent scene:didInitializeWithEvent:completion:] + 361 26 FrontBoardServices 0x00007fff364e0361 -[FBSSceneImpl _callOutQueue_agent_didCreateWithTransitionContext:completion:] + 442 27 FrontBoardServices 0x00007fff365065f8 __86-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]_block_invoke.154 + 102 28 FrontBoardServices 0x00007fff364eae41 -[FBSWorkspace _calloutQueue_executeCalloutFromSource:withBlock:] + 220 29 FrontBoardServices 0x00007fff36506289 __86-[FBSWorkspaceScenesClient sceneID:createWithParameters:transitionContext:completion:]_block_invoke + 355 30 libdispatch.dylib 0x000000011097ad6c _dispatch_client_callout + 8 31 libdispatch.dylib 0x000000011097dcdd _dispatch_block_invoke_direct + 300 32 FrontBoardServices 0x00007fff3652c49e __FBSSERIALQUEUE_IS_CALLING_OUT_TO_A_BLOCK__ + 30 33 FrontBoardServices 0x00007fff3652c18c -[FBSSerialQueue _queue_performNextIfPossible] + 441 34 FrontBoardServices 0x00007fff3652c69b -[FBSSerialQueue _performNextFromRunLoopSource] + 22 35 CoreFoundation 0x00007fff23b0d271 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 17 36 CoreFoundation 0x00007fff23b0d19c __CFRunLoopDoSource0 + 76 37 CoreFoundation 0x00007fff23b0c974 __CFRunLoopDoSources0 + 180 38 CoreFoundation 0x00007fff23b0767f __CFRunLoopRun + 1263 39 CoreFoundation 0x00007fff23b06e66 CFRunLoopRunSpecific + 438 40 GraphicsServices 0x00007fff38346bb0 GSEventRunModal + 65 41 UIKitCore 0x00007fff47578dd0 UIApplicationMain + 1621 42 HBuilder 0x000000010c520c00 main + 112 43 libdyld.dylib 0x00007fff516ecd29 start + 1 ) 手动集成的weixinSDK,一开始还以为是other linker flag填写错误 加上了-ObjC -all_load都不行
2019-10-30+ (void)startLogByLevel:(WXLogLevel)level logBlock:(WXLogBolock)logBlock; register前调用WXApi这个接口检查SDK输出的报错提示
微信SDK1.8.6,registerApp返回False[图片] 调用方法向微信注册应用时返回False,我这边根据官方文档的引导一步一步的进行了操作。 目前可以确定几点: 1.已在微信开放平台填写的universal link 2.universal link测试通过(我可以在记事本中点击链接跳转到App) 3.LSApplicationQueriesSchemes中包含weixin及weixinULAPI
2019-10-18请检查工程文件中选择 Build Setting,在"Other Linker Flags"中是否已经添加了"-ObjC -all_load" 详情请参考接入文档3.2的第4点 https://developers.weixin.qq.com/doc/oplatform/Mobile_App/Access_Guide/iOS.html
ios集成新的微信SDK后登录报错?2019-10-09 18:38:11.086615+0800 proj-mobile[1408:423767] log : wxlog:set property list 2019-10-09 18:38:11.095783+0800 proj-mobile[1408:423767] +[WXApi genExtraUrlByReq:withAppData:]: unrecognized selector sent to class 0x103a5aa30 2019-10-09 18:38:11.095991+0800 proj-mobile[1408:423767] EXCEPTION THROW: +[WXApi genExtraUrlByReq:withAppData:]: unrecognized selector sent to class 0x103a5aa30 wxLogin throw: {} 2019-10-09 18:38:11.096207+0800 proj-mobile[1408:423767] HelloOC: wxLogin throw: {} 错误如下,点击登录后报错。求教
2019-10-16首先出现该确认框是由于微信使用universal link返回app失败了,因此微信出二次确认授权,降级使用scheme拉起app. 问题1: 点击取消没有返回app是微信app的问题,我们会在后续版本修复 问题2:正常表现. 因为使用的是scheme协议 问题3: 基于universal link无法拉起app的情况,表现符合预期 问题4: 请尝试使用你们的universal link+path+任意字符串,在safari发起请求看是否能识别打开app, 以确认universal link配置ok. 详见文档https://developers.weixin.qq.com/doc/oplatform/Mobile_App/Access_Guide/iOS.html
ios sdk 1.8.6.1 授权登录没有回调 onResp ?IOS SDK 1.8.6.1 SendAuthReq 调用之后 如果是确定授权 onResp 会被正常吊起,正常回调 APP。 问题 1. 如果是取消(拒绝授权) onResp 没有被 调用?并且就停留在微信页面,不回调 APP 问题 2. app 被回调走的 openurl 方法不是 link 方法 (link 已经配置) 问题 3 请确认吊起的页面是否正确 问题 4 apple-app-site-association文件是否正确? { "applinks": { "apps": [], "details": [ { "appID": "******.com.goockr.********",(可以确保是 teamid.bundleid) "paths": [ "*" ] } ] } } 环境 微信 7.0.8 ios 13.1.1 微信 appid wxf54b36ad0a35ce54 打印日志 2019-10-15 14:50:18.542662+0800 GoockrCharging[509:45639] wxlog : wxlog:send req[<SendAuthReq: 0x28255d890>], appID:wxf54b36ad0a35ce54, universalLink:https://chhp.goockr.com/, sdkVersion:1.8.6.1 2019-10-15 14:50:18.563918+0800 GoockrCharging[509:45639] wxlog : wxlog:set property list 2019-10-15 14:50:18.596720+0800 GoockrCharging[509:45639] wxlog : wxlog:Error:fail to load Keychain status:-25300, keyData null:1 2019-10-15 14:50:18.596814+0800 GoockrCharging[509:45639] wxlog : wxlog:Error:token[(null)] is null 2019-10-15 14:50:18.629768+0800 GoockrCharging[509:45639] wxlog : wxlog:launch app with ul only success 2019-10-15 14:50:18.629883+0800 GoockrCharging[509:45639] wxlog : wxlog:launch app with universal link, ret:1 2019-10-15 14:50:18.629944+0800 GoockrCharging[509:45639] wxlog : wxlog:req:<SendAuthReq: 0x28255d890>, cid:c3dd703a982028a5a3115d55e707118bbc9d2522 2019-10-15 14:50:18.796704+0800 GoockrCharging[509:46989] PBItemCollectionServicer connection disconnected. 2019-10-15 14:50:19.463485+0800 GoockrCharging[509:45639] Can't end BackgroundTask: no background task exists with identifier 6 (0x6), or it may have already been ended. Break in UIApplicationEndBackgroundTaskError() to debug. 以下页面是授权登录吊起的页面 是否正确? [图片]
2019-10-15在safari 输入 weixin:// 可以打开微信吗?
升级了最新的SDK,微信分享调不起来界面?首先是出现这个: -canOpenURL: failed for URL: "weixinULAPI://" - error: "This app is not allowed to query for scheme weixinulapi" 然后我在白名单中配置了weixinULAPI 之后,没有打印上面的错误了,但是还是没有调起来微信的页面。
2019-10-14请问微信支付、登录、分享有这个表现吗?
iOS微信升级SDK1.8.6.1后,部分设备无法使用微信支付、登录、分享功能iOS微信升级到SDK1.8.6.1后,部分设备在更新后启动时没有拉取到universal links信息,导致进入微信就立即返回app,能获取到universal links的设备一切正常,微信这边有没有什么兼容处理
2019-10-12你好,path要传“query?cdkey=xxxx”这种格式才能被成功解析
移动应用拉起小游戏参数无法获取移动应用可以拉起小游戏,官方有文档: https://open.weixin.qq.com/cgi-bin/showdocument?action=dir_list&t=resource/res_list&verify=1&id=21526646385rK1Bs&token=5d0460853e4058cda3c86f93ad697853eed084be&lang=zh_CN 项目中碰到一个业务,通过app打开小游戏,当path路径为空时可以正常打开小游戏,但当path传递参数,比如path的值为"?a=xxx"时,小游戏无法获取到参数a,在另外一个小程序里,却可以正常获取参数,代码如下: wx.navigateToMiniProgram({ appId: 'XXXXXX', path:"?cdkey=xxxxx", envVersion: 'release', success(res) { console.log("小游戏打开ok"); } }) 经测试,app打开小程序,使用完整的path路径,比如“/pages/home/home?para1=xxx”时,可以正常获取到para1参数, 奇怪,为何小游戏获取不到参数??唯一的差别:小游戏没有类似“pages/home/home”这样的path,只要有query. 针对上面问题,我们也尝试在app端,也升级了微信小程序的最新sdk,通过app拉起小游戏时,仍然时获取不到参数, 请问下,这个如何解决??
2019-07-30这个是微信openSDK的MTA在应用启动时对剪切板的访问和其他SDK竞争导致的crash 关闭MTA可以暂时规避此问题
微信分享ios-getaddrinfo崩溃- 当前 Bug 的表现(可附上截图) [图片] [图片] [图片] - 预期表现 通过bugly搜集到的崩溃日志 - 复现路径 暂时没法复现 什么情况下会触发这种崩溃?
2019-06-25请提供一下发生错误的截图、app的bundleId以及微信侧发生错误的微信号
App跳转小程序跳转失败- 当前 Bug 的表现(可附上截图) 跳转失败 - 预期表现 跳转成功 - 复现路径 点击跳转 - 提供一个最简复现 Demo WXLaunchMiniProgramReq *launchMiniProgramReq = [WXLaunchMiniProgramReq object]; launchMiniProgramReq.userName = @"gh_60b2f8c1a577"; //拉起的小程序的username launchMiniProgramReq.path = @"pages/index/tenant/enter?id=0d557c61d5d8927fed28c639205fb03b"; //拉起小程序页面的可带参路径,不填默认拉起小程序首页 launchMiniProgramReq.miniProgramType = WXMiniProgramTypeRelease; //拉起小程序的类型 return [WXApi sendReq:launchMiniProgramReq];
2018-11-14能否提供一下复现问题的步骤和代码片段?
小程序跳转iOS端 iOS端无法接参官方文档里面就一句 <button open-type="launchApp" app-parameter="wechat" binderror="launchAppError">打开APP-main</button> iOS端无法接到小程序app-parameter中的参数 安卓端无问题
2018-11-13