使用移动开发套件MDK CLIENT 3.2.5构建Android的SAP Asset Manager时出错

2020-08-21 19:46发布

点击此处---> 群内免费提供SAP练习系统(在群公告中)加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)尊敬的专家, 我已经设置了一个...

         点击此处--->   EasySAP.com群内免费提供SAP练习系统(在群公告中)

加入QQ群:457200227(SAP S4 HANA技术交流) 群内免费提供SAP练习系统(在群公告中)


尊敬的专家,

我已经设置了一个构建环境来构建SAP Asset Manager移动应用程序。 我已经成功构建了iOS应用,但是构建Android版本时出现以下错误。

"找不到与包名称'com.xxx.meridia.swim.AssetManager匹配的客户端""

构建过程正在生成一个带有" package_name"的google-service.json文件:" com.sap.mobile.apps.assetmanager.release"

在AndroidManifest.xml中,程序包=" com.xxx.meridia.swim.AssetManager"

感谢您的帮助。 问候。

构建环境

**********************
移动开发套件MDK CLIENT 3.2.5 ==> MDKCLNTSDK3002P_5-70003511.ZIP

SAP中SAP Asset Manager 4.0.3的元数据==> ASTMNGRMETDATA00_3-80004744.ZIP

资产管理器品牌SDK 4.0 ==> ASSET_MNGR_SDK00_0-80004732.ZIP

用于iOS 00 4的资产管理器插件SDK => SAM_EXTSN_SDK00_4-70004601.ZIP

用于Android 00 4的资产管理器插件SDK => MDK_PLGSDK_AND00P_4-70004602.ZIP

完全例外

****************

org.gradle.api.tasks.TaskExecutionException:任务':app:processDebugGoogleServices'的执行失败。 在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:110)在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:77)在org.gradle org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter.execute(SkipUpToDateTaskExecuter.java:59)上的.api.internal.tasks.execution.OutputDirectoryCreatingTaskExecuter.execute(OutputDirectoryCreatingTaskExecuter.java:51) org.gradle.api.internal.tasks.execution.ValidatingTaskExecuter.execute(ValidatingTaskExecuter.java:59)的.tasks.execution.ResolveTaskOutputCachingStateExecuter.execute(ResolveTaskOutputCachingStateExecuter.java:54)at org.gradle.api.internal.tasks.execution org.gradle.api.internal.tasks.execution.FinalizeInputFilePropertiesTaskExecuter.execute(FinalizeInputFilePropertiesTaskExecuter.java:44)处的.SkipEmptySourceFilesTaskExecuter.execute(SkipEmptySourceFilesTaskExecuter.java:101) org.gradle.api.internal.tasks.execution.ResolveTaskArtifactStateTaskExecuter.execute(ResolveTaskArtifactStateTaskExecuter.java:62)在org.gradle.api上的.api.internal.tasks.execution.CleanupStaleOutputsExecuter.java.91(CleanupStaleOutputsExecuter.java:91)。 org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:54)上的.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:59)在org.gradle.api.internal.task中 org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:34)处的ExecuteAtMostOnceTaskExecuter.execute(ExecuteAtMostOnceTaskExecuter.java:43)在org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter $ 1。 在org.gradle.internal.operations.DefaultBuildOperationE上运行(EventFiringTaskExecuter.java:51)在org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300) org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)处的xecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)在org.gradle.internal.operations.DefaultBuildOecationExecutor.run(DefaultBuild.OperationExecutor.90): 在org.gradle.execution.taskgraph上的org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:46)上的org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31) org.gradle.execution.taskgraph.DefaultTaskExecutionGraph $ BuildOperationAwareWorkItemExecutor.execute(DefaultTaskExecutionGraph.java:277)上的org.gradle.execution.taskute.LocalTask​​InfoExecutor.execute(LocalTask​​InfoExecutor.java:42) :262)at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker $ 1.execute(DefaultTaskPlanEx ecutor.java:135)at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker $ 1.execute(DefaultTaskPlanExecutor.java:130)at org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.execute(DefaultTaskPlanExecutor.java:200) org.gradle.internal.concurrent上的org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.run(DefaultTaskPlanExecutor.java:130)上的org.gradle.execution.taskgraph.DefaultTaskPlanExecutor $ ExecutorWorker.executeWithWork(DefaultTaskPlanExecutor.java:191) 在org.gradle.internal.concurrent.ManagedExecutorImpl $ 1.run(ManagedExecutorImpl.java:46)处的ExecutorPolicy $ CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)在java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) org.gradle.internal.concurrent.ThreadFactoryImpl $ ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)处的java.util.concurrent.ThreadPoolExecutor $ Worker.run(ThreadPoolExecutor.java:624)在java.lang.Thread.run(Thread。 java:748)由以下原因引起: org.gradle.api.GradleException:在sun.reflect上未找到com.google.gms.googleservices.GoogleServicesTask.action(GoogleServicesTask.java:114)上名为" com.xxx.meridia.swim.AssetManager"的包名称的匹配客户端。 位于sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)处的NativeMethodAccessorImpl.invoke0(本地方法),位于java.lang.reflect.Method.invoke(Method.java.43)处的sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)处的NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) org.gradle.internal.reflect.JavaMethod.invoke(javaMethod.java:73)处org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:46)处org.gradle org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26)位于org.gradle.api.internal的.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39) org.gradle.api.internal.AbstractTask $ TaskAction上的.AbstractTask $ TaskActionWrapper.execute(AbstractTask.java:801) Wrapper.execute(AbstractTask.java:768)位于org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter $ 1.run(ExecuteActionsTaskExecuter.java:131)位于org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor .java:300),位于org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174),位于org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174),位于org.gradle.internal.operations.DefaultBuildOperationExecutor $ RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)。 内部操作.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)位于org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31),位于org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter。 ExecuteActionsTaskExecuter.java:120)在org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.j ava:99)...还有34个

2条回答
小熊yu生菜
2020-08-21 20:20 .采纳回答

Didier

如果您要使用其他捆绑软件ID构建自己的客户端,则还需要为捆绑软件ID设置推送支持,并相应地更新google-service.json文件。 SDK随附的文件假定您使用的是默认捆绑商品ID。

-账单

一周热门 更多>