2013-04-25 16:02:17 +02:00
|
|
|
/****************************************************************************
|
|
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** Copyright (C) 2016 The Qt Company Ltd.
|
|
|
|
|
** Contact: https://www.qt.io/licensing/
|
2013-04-25 16:02:17 +02:00
|
|
|
**
|
|
|
|
|
** This file is part of Qt Creator.
|
|
|
|
|
**
|
|
|
|
|
** Commercial License Usage
|
|
|
|
|
** Licensees holding valid commercial Qt licenses may use this file in
|
|
|
|
|
** accordance with the commercial license agreement provided with the
|
|
|
|
|
** Software or, alternatively, in accordance with the terms contained in
|
2016-01-15 14:57:40 +01:00
|
|
|
** a written agreement between you and The Qt Company. For licensing terms
|
|
|
|
|
** and conditions see https://www.qt.io/terms-conditions. For further
|
|
|
|
|
** information use the contact form at https://www.qt.io/contact-us.
|
2013-04-25 16:02:17 +02:00
|
|
|
**
|
2016-01-15 14:57:40 +01:00
|
|
|
** GNU General Public License Usage
|
|
|
|
|
** Alternatively, this file may be used under the terms of the GNU
|
|
|
|
|
** General Public License version 3 as published by the Free Software
|
|
|
|
|
** Foundation with exceptions as appearing in the file LICENSE.GPL3-EXCEPT
|
|
|
|
|
** included in the packaging of this file. Please review the following
|
|
|
|
|
** information to ensure the GNU General Public License requirements will
|
|
|
|
|
** be met: https://www.gnu.org/licenses/gpl-3.0.html.
|
2013-04-25 16:02:17 +02:00
|
|
|
**
|
|
|
|
|
****************************************************************************/
|
|
|
|
|
|
|
|
|
|
#include "iosdeploystep.h"
|
|
|
|
|
#include "iosbuildstep.h"
|
|
|
|
|
#include "iosconstants.h"
|
|
|
|
|
#include "iosrunconfiguration.h"
|
|
|
|
|
#include "iostoolhandler.h"
|
|
|
|
|
|
|
|
|
|
#include <coreplugin/messagemanager.h>
|
2019-04-23 18:18:03 +02:00
|
|
|
|
2013-04-25 16:02:17 +02:00
|
|
|
#include <projectexplorer/buildconfiguration.h>
|
|
|
|
|
#include <projectexplorer/projectexplorerconstants.h>
|
|
|
|
|
#include <projectexplorer/target.h>
|
2013-11-04 22:45:52 +01:00
|
|
|
#include <projectexplorer/taskhub.h>
|
2014-05-13 16:09:11 +02:00
|
|
|
#include <projectexplorer/kitmanager.h>
|
|
|
|
|
#include <projectexplorer/kitinformation.h>
|
|
|
|
|
#include <projectexplorer/devicesupport/devicemanager.h>
|
2013-04-25 16:02:17 +02:00
|
|
|
|
|
|
|
|
#include <qtsupport/qtkitinformation.h>
|
|
|
|
|
|
2017-01-19 16:44:22 +01:00
|
|
|
#include <utils/temporaryfile.h>
|
|
|
|
|
|
2013-04-25 16:02:17 +02:00
|
|
|
#include <QDir>
|
2014-05-08 13:43:25 +02:00
|
|
|
#include <QFile>
|
|
|
|
|
#include <QSettings>
|
2013-04-25 16:02:17 +02:00
|
|
|
|
|
|
|
|
#define ASSERT_STATE(state) ASSERT_STATE_GENERIC(State, state, m_state)
|
|
|
|
|
|
|
|
|
|
using namespace ProjectExplorer;
|
2019-05-15 15:49:19 +02:00
|
|
|
using namespace Utils;
|
2013-04-25 16:02:17 +02:00
|
|
|
|
|
|
|
|
namespace Ios {
|
|
|
|
|
namespace Internal {
|
|
|
|
|
|
2019-12-20 17:05:30 +01:00
|
|
|
IosDeployStep::IosDeployStep(BuildStepList *parent, Core::Id id)
|
|
|
|
|
: BuildStep(parent, id)
|
2013-04-25 16:02:17 +02:00
|
|
|
{
|
2018-10-22 17:56:04 +02:00
|
|
|
setImmutable(true);
|
2014-05-13 16:09:11 +02:00
|
|
|
updateDisplayNames();
|
2016-06-29 19:35:23 +03:00
|
|
|
connect(DeviceManager::instance(), &DeviceManager::updated,
|
|
|
|
|
this, &IosDeployStep::updateDisplayNames);
|
|
|
|
|
connect(target(), &Target::kitChanged,
|
|
|
|
|
this, &IosDeployStep::updateDisplayNames);
|
2014-05-13 16:09:11 +02:00
|
|
|
}
|
|
|
|
|
|
2019-01-18 11:32:53 +01:00
|
|
|
Core::Id IosDeployStep::stepId()
|
|
|
|
|
{
|
|
|
|
|
return "Qt4ProjectManager.IosDeployStep";
|
|
|
|
|
}
|
|
|
|
|
|
2014-05-13 16:09:11 +02:00
|
|
|
void IosDeployStep::updateDisplayNames()
|
|
|
|
|
{
|
2015-02-03 23:49:46 +02:00
|
|
|
IDevice::ConstPtr dev =
|
2019-02-06 12:50:51 +01:00
|
|
|
DeviceKitAspect::device(target()->kit());
|
2014-05-13 16:09:11 +02:00
|
|
|
const QString devName = dev.isNull() ? IosDevice::name() : dev->displayName();
|
2013-04-25 16:02:17 +02:00
|
|
|
setDefaultDisplayName(tr("Deploy to %1").arg(devName));
|
2014-05-13 16:09:11 +02:00
|
|
|
setDisplayName(tr("Deploy to %1").arg(devName));
|
2013-04-25 16:02:17 +02:00
|
|
|
}
|
|
|
|
|
|
2019-01-10 15:31:44 +01:00
|
|
|
bool IosDeployStep::init()
|
2013-04-25 16:02:17 +02:00
|
|
|
{
|
2014-05-13 16:09:11 +02:00
|
|
|
QTC_ASSERT(m_transferStatus == NoTransfer, return false);
|
2019-02-06 12:50:51 +01:00
|
|
|
m_device = DeviceKitAspect::device(target()->kit());
|
2018-11-12 19:55:59 +01:00
|
|
|
auto runConfig = qobject_cast<const IosRunConfiguration *>(
|
|
|
|
|
this->target()->activeRunConfiguration());
|
2014-05-17 22:53:00 +02:00
|
|
|
QTC_ASSERT(runConfig, return false);
|
2019-05-15 15:49:19 +02:00
|
|
|
m_bundlePath = runConfig->bundleDirectory();
|
2016-09-26 12:40:09 +02:00
|
|
|
|
|
|
|
|
if (iosdevice()) {
|
|
|
|
|
m_deviceType = IosDeviceType(IosDeviceType::IosDevice, deviceId());
|
|
|
|
|
} else if (iossimulator()) {
|
|
|
|
|
m_deviceType = runConfig->deviceType();
|
|
|
|
|
} else {
|
2013-10-07 16:07:16 +02:00
|
|
|
emit addOutput(tr("Error: no device available, deploy failed."),
|
2017-01-12 10:59:12 +01:00
|
|
|
BuildStep::OutputFormat::ErrorMessage);
|
2013-10-07 16:07:16 +02:00
|
|
|
return false;
|
|
|
|
|
}
|
2013-04-25 16:02:17 +02:00
|
|
|
return true;
|
|
|
|
|
}
|
|
|
|
|
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
void IosDeployStep::doRun()
|
2013-04-25 16:02:17 +02:00
|
|
|
{
|
|
|
|
|
QTC_CHECK(m_transferStatus == NoTransfer);
|
2016-09-26 12:40:09 +02:00
|
|
|
if (device().isNull()) {
|
2020-01-15 08:56:11 +01:00
|
|
|
TaskHub::addTask(
|
|
|
|
|
DeploymentTask(Task::Error, tr("Deployment failed. No iOS device found.")));
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
emit finished(!iossimulator().isNull());
|
2013-04-25 16:02:17 +02:00
|
|
|
cleanup();
|
|
|
|
|
return;
|
|
|
|
|
}
|
2016-09-26 12:40:09 +02:00
|
|
|
m_toolHandler = new IosToolHandler(m_deviceType, this);
|
2013-04-25 16:02:17 +02:00
|
|
|
m_transferStatus = TransferInProgress;
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
emit progress(0, tr("Transferring application"));
|
2016-06-29 19:35:23 +03:00
|
|
|
connect(m_toolHandler, &IosToolHandler::isTransferringApp,
|
|
|
|
|
this, &IosDeployStep::handleIsTransferringApp);
|
|
|
|
|
connect(m_toolHandler, &IosToolHandler::didTransferApp,
|
|
|
|
|
this, &IosDeployStep::handleDidTransferApp);
|
|
|
|
|
connect(m_toolHandler, &IosToolHandler::finished,
|
|
|
|
|
this, &IosDeployStep::handleFinished);
|
|
|
|
|
connect(m_toolHandler, &IosToolHandler::errorMsg,
|
|
|
|
|
this, &IosDeployStep::handleErrorMsg);
|
2014-05-08 13:43:25 +02:00
|
|
|
checkProvisioningProfile();
|
2019-05-15 15:49:19 +02:00
|
|
|
m_toolHandler->requestTransferApp(m_bundlePath.toString(), m_deviceType.identifier);
|
2013-04-25 16:02:17 +02:00
|
|
|
}
|
|
|
|
|
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
void IosDeployStep::doCancel()
|
2013-04-25 16:02:17 +02:00
|
|
|
{
|
|
|
|
|
if (m_toolHandler)
|
|
|
|
|
m_toolHandler->stop();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void IosDeployStep::cleanup()
|
|
|
|
|
{
|
|
|
|
|
QTC_CHECK(m_transferStatus != TransferInProgress);
|
|
|
|
|
m_transferStatus = NoTransfer;
|
|
|
|
|
m_device.clear();
|
2016-09-26 12:40:09 +02:00
|
|
|
m_toolHandler = nullptr;
|
2014-05-08 13:43:25 +02:00
|
|
|
m_expectFail = false;
|
2013-04-25 16:02:17 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void IosDeployStep::handleIsTransferringApp(IosToolHandler *handler, const QString &bundlePath,
|
|
|
|
|
const QString &deviceId, int progress, int maxProgress,
|
|
|
|
|
const QString &info)
|
|
|
|
|
{
|
2019-07-23 10:58:00 +02:00
|
|
|
Q_UNUSED(handler); Q_UNUSED(bundlePath); Q_UNUSED(deviceId)
|
2013-04-25 16:02:17 +02:00
|
|
|
QTC_CHECK(m_transferStatus == TransferInProgress);
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
emit this->progress(progress * 100 / maxProgress, info);
|
2013-04-25 16:02:17 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void IosDeployStep::handleDidTransferApp(IosToolHandler *handler, const QString &bundlePath,
|
|
|
|
|
const QString &deviceId, IosToolHandler::OpStatus status)
|
|
|
|
|
{
|
2019-07-23 10:58:00 +02:00
|
|
|
Q_UNUSED(handler); Q_UNUSED(bundlePath); Q_UNUSED(deviceId)
|
2013-04-25 16:02:17 +02:00
|
|
|
QTC_CHECK(m_transferStatus == TransferInProgress);
|
2013-11-04 22:45:52 +01:00
|
|
|
if (status == IosToolHandler::Success) {
|
2013-04-25 16:02:17 +02:00
|
|
|
m_transferStatus = TransferOk;
|
2013-11-04 22:45:52 +01:00
|
|
|
} else {
|
2013-04-25 16:02:17 +02:00
|
|
|
m_transferStatus = TransferFailed;
|
2014-05-08 13:43:25 +02:00
|
|
|
if (!m_expectFail)
|
2020-01-15 08:56:11 +01:00
|
|
|
TaskHub::addTask(DeploymentTask(Task::Error,
|
|
|
|
|
tr("Deployment failed. The settings in the Devices window of Xcode might be incorrect.")));
|
2013-11-04 22:45:52 +01:00
|
|
|
}
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
emit finished(status == IosToolHandler::Success);
|
2013-04-25 16:02:17 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
void IosDeployStep::handleFinished(IosToolHandler *handler)
|
|
|
|
|
{
|
|
|
|
|
switch (m_transferStatus) {
|
|
|
|
|
case TransferInProgress:
|
|
|
|
|
m_transferStatus = TransferFailed;
|
2020-01-15 08:56:11 +01:00
|
|
|
TaskHub::addTask(DeploymentTask(Task::Error, tr("Deployment failed.")));
|
ProjectExplorer: Rework the build step run interface
Originally, the build manager used to run all build steps in a dedicated
thread. Communication between the step and the manager happened via a
QFutureInterface that was passed into the step's run() function.
Later, new steps were added that operated asynchronously, so the build
manager had to differentiate between the different kinds of steps for
starting and stopping.
These days, almost all build and deploy steps work asynchronously, which
made the QFuture-based interface look increasingly odd.
With this patch, all build steps are expected to work asynchronously, so
the build manager no longer needs to differentiate. Steps are started
and requested to stop via the run() and cancel() functions,
respectively, and emit the finished() signal when they are done. Build
step implementors no longer have to deal with a QFutureInterface. For
steps whose implementation is inherently synchronous, the BuildStep base
class offers a runInThread() function.
Change-Id: If905c68b234c5a669f6e19f43142eaa57d594803
Reviewed-by: hjk <hjk@qt.io>
2019-01-25 14:26:34 +01:00
|
|
|
emit finished(false);
|
2013-04-25 16:02:17 +02:00
|
|
|
break;
|
|
|
|
|
case NoTransfer:
|
|
|
|
|
case TransferOk:
|
|
|
|
|
case TransferFailed:
|
|
|
|
|
break;
|
|
|
|
|
}
|
|
|
|
|
cleanup();
|
|
|
|
|
handler->deleteLater();
|
|
|
|
|
// move it when result is reported? (would need care to avoid problems with concurrent runs)
|
|
|
|
|
}
|
|
|
|
|
|
2013-10-07 16:07:16 +02:00
|
|
|
void IosDeployStep::handleErrorMsg(IosToolHandler *handler, const QString &msg)
|
|
|
|
|
{
|
2019-07-23 10:58:00 +02:00
|
|
|
Q_UNUSED(handler)
|
2013-11-04 22:45:52 +01:00
|
|
|
if (msg.contains(QLatin1String("AMDeviceInstallApplication returned -402653103")))
|
2020-01-15 08:56:11 +01:00
|
|
|
TaskHub::addTask(DeploymentTask(Task::Warning, tr("The Info.plist might be incorrect.")));
|
|
|
|
|
|
2017-01-12 10:59:12 +01:00
|
|
|
emit addOutput(msg, BuildStep::OutputFormat::ErrorMessage);
|
2013-10-07 16:07:16 +02:00
|
|
|
}
|
|
|
|
|
|
2013-04-25 16:02:17 +02:00
|
|
|
BuildStepConfigWidget *IosDeployStep::createConfigWidget()
|
|
|
|
|
{
|
2019-04-23 18:18:03 +02:00
|
|
|
auto widget = new BuildStepConfigWidget(this);
|
|
|
|
|
|
|
|
|
|
widget->setObjectName("IosDeployStepWidget");
|
|
|
|
|
widget->setDisplayName(QString("<b>%1</b>").arg(displayName()));
|
|
|
|
|
widget->setSummaryText(widget->displayName());
|
|
|
|
|
|
|
|
|
|
connect(this, &ProjectConfiguration::displayNameChanged,
|
|
|
|
|
widget, &BuildStepConfigWidget::updateSummary);
|
|
|
|
|
|
|
|
|
|
return widget;
|
2013-04-25 16:02:17 +02:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
QString IosDeployStep::deviceId() const
|
|
|
|
|
{
|
|
|
|
|
if (iosdevice().isNull())
|
|
|
|
|
return QString();
|
|
|
|
|
return iosdevice()->uniqueDeviceID();
|
|
|
|
|
}
|
|
|
|
|
|
2014-05-08 13:43:25 +02:00
|
|
|
void IosDeployStep::checkProvisioningProfile()
|
|
|
|
|
{
|
|
|
|
|
IosDevice::ConstPtr device = iosdevice();
|
|
|
|
|
if (device.isNull())
|
|
|
|
|
return;
|
|
|
|
|
|
2019-05-28 13:49:26 +02:00
|
|
|
const FilePath provisioningFilePath = m_bundlePath.pathAppended("embedded.mobileprovision");
|
2014-05-08 13:43:25 +02:00
|
|
|
|
|
|
|
|
// the file is a signed plist stored in DER format
|
|
|
|
|
// we simply search for start and end of the plist instead of decoding the DER payload
|
2014-10-24 13:15:54 +02:00
|
|
|
if (!provisioningFilePath.exists())
|
2014-05-08 13:43:25 +02:00
|
|
|
return;
|
|
|
|
|
QFile provisionFile(provisioningFilePath.toString());
|
|
|
|
|
if (!provisionFile.open(QIODevice::ReadOnly))
|
|
|
|
|
return;
|
|
|
|
|
QByteArray provisionData = provisionFile.readAll();
|
|
|
|
|
int start = provisionData.indexOf("<?xml version=\"1.0\" encoding=\"UTF-8\"?>");
|
|
|
|
|
int end = provisionData.indexOf("</plist>");
|
|
|
|
|
if (start == -1 || end == -1)
|
|
|
|
|
return;
|
|
|
|
|
end += 8;
|
|
|
|
|
|
2017-01-19 16:44:22 +01:00
|
|
|
Utils::TemporaryFile f("iosdeploy");
|
2014-05-08 13:43:25 +02:00
|
|
|
if (!f.open())
|
|
|
|
|
return;
|
|
|
|
|
f.write(provisionData.mid(start, end - start));
|
|
|
|
|
f.flush();
|
|
|
|
|
QSettings provisionPlist(f.fileName(), QSettings::NativeFormat);
|
|
|
|
|
|
|
|
|
|
if (!provisionPlist.contains(QLatin1String("ProvisionedDevices")))
|
|
|
|
|
return;
|
|
|
|
|
QStringList deviceIds = provisionPlist.value(QLatin1String("ProvisionedDevices")).toStringList();
|
|
|
|
|
QString targetId = device->uniqueDeviceID();
|
|
|
|
|
foreach (const QString &deviceId, deviceIds) {
|
|
|
|
|
if (deviceId == targetId)
|
|
|
|
|
return;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
m_expectFail = true;
|
|
|
|
|
QString provisioningProfile = provisionPlist.value(QLatin1String("Name")).toString();
|
|
|
|
|
QString provisioningUid = provisionPlist.value(QLatin1String("UUID")).toString();
|
2020-01-15 08:56:11 +01:00
|
|
|
CompileTask task(Task::Warning,
|
2014-05-08 13:43:25 +02:00
|
|
|
tr("The provisioning profile \"%1\" (%2) used to sign the application "
|
|
|
|
|
"does not cover the device %3 (%4). Deployment to it will fail.")
|
|
|
|
|
.arg(provisioningProfile, provisioningUid, device->displayName(),
|
2020-01-15 08:56:11 +01:00
|
|
|
targetId));
|
2014-05-08 13:43:25 +02:00
|
|
|
emit addTask(task);
|
|
|
|
|
}
|
|
|
|
|
|
2013-04-25 16:02:17 +02:00
|
|
|
IDevice::ConstPtr IosDeployStep::device() const
|
|
|
|
|
{
|
|
|
|
|
return m_device;
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
IosDevice::ConstPtr IosDeployStep::iosdevice() const
|
|
|
|
|
{
|
|
|
|
|
return m_device.dynamicCast<const IosDevice>();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
IosSimulator::ConstPtr IosDeployStep::iossimulator() const
|
|
|
|
|
{
|
|
|
|
|
return m_device.dynamicCast<const IosSimulator>();
|
|
|
|
|
}
|
|
|
|
|
|
|
|
|
|
} // namespace Internal
|
2013-10-16 11:02:37 +02:00
|
|
|
} // namespace Ios
|